Add production configuration support
must opened this issue · comments
Add support for production configuration that only loads on production and is not committed to the repo.
committing to [a] repo is a choice outside the scope of the platform as it does not handle version control itself.
The point was about being able to distinguish between production configuration and development configuration or env dependent configuration in this case (it does include what you commit to the repo but also this means having a hidden version of config that is not committed (as in ignored) and which should be initially done by the platform's repo for people who just clone it for example)
all of the files generated by the platform are git-ignored in the default boilerplate projects, including the now separate production config alongside the old general config.