I’m working to upgrade our Ghost application from 0.11 to 1.22 via Docker & Docker Compose. We’d like to support 3 separate environments: development, QA and production.
I’ve read through the information on Ghost’s config and saw your forum response on Config.js vs config.production.json, where you mention that config can be set up by “supplying both environment variables & command line arguments instead of values in the file”.
What is the recommended approach is for configuring a QA/staging environment? We have a different “url” and a different “database” option, however, since we want our QA environment to mimic our production environment as closely as possible, I’m thinking we’d still like to set
How do you recommend we override the database config in config.production.json? Can we create some sort of config.qa.json? Should we pass in environment variables via our docker-compose.yml files (we already do that for S3 configuration)?. Or do you propose adding conditionals to our Dockerfile that supply the configuration via command line arguments?
Thank you in advance!