lax #5176 make a cleaner module [resolved]

The module should only be a skeleton that shows what the developper is able to customize.

The configuration part (i.e. what components are included, what kind of authentication is used, etc.) should go in a separate module, say

The application schema should be loaded transparently by the module. could define a postinit callback that would be called by once everything is loaded.

appeared in<not specified>
done in0.3.0
load left0.000
closed by<not specified>