Subscribie-deployer sets the initial settings and config needed for a new shop during sign-up. You don't need this to run Subscribie locally. You do need this if you want to work on the onboarding/sign-up process.
Currently every shop has its own .ini vassal file, yet they are all the same (apart from the shop name).
Why does this matter? Because changing uwsgi config , or adding config for all vassals is overly complex when there is 1 ini file for each vassal (it has now reached the point that it does not scale).
Use uwsgi vassal templating to have one vassal template to simplify operations.
Currently every shop has its own .ini vassal file, yet they are all the same (apart from the shop name).
Why does this matter? Because changing uwsgi config , or adding config for all vassals is overly complex when there is 1
inifile for each vassal (it has now reached the point that it does not scale).Use uwsgi vassal templating to have one vassal template to simplify operations.
See "
--vassals-include" which may be set in the emperor config, which is then injected into all vassals. Src: https://uwsgi-docs.readthedocs.io/en/latest/Configuration.html#magic-variablesAs a operator use uwsgi template for vassals so that vassal config is in one file
Related https://github.com/Subscribie/subscribie/issues/801