Init phase for djangoldp modules
Some modules need to initialize data. For example, djangoldp_account
requires to add a middleware in config and execute a registration phase (see doc).
Asking to the sib-manager
to know all about every single module initialization seems to break the distributed pattern. The initialization phase may require some input from the admin so we can't rely on migrations to execute it. Should we have a specific command in each package with the appropriate code to setup the LDP module ?
We have a similar issue to setup and maintain the ldpsources
for all the modules. An easy way to handle it could be its integration inside the packages.yml as a list of list of sources. But it would require to load the sources from the settings and modifications to this list will require to reload the server (this would be a regression in comparison to managing this sources' list from the backend).
Alternatively we could manage to setup a "default" list of sources at deployment as fixtures, then rely on the backend to manage them.
@sylvain @bleme @jbpasquier @alexandre Do you have insights on this ?