Ghost is version 3.14.0.
I would like to use a file named something other than config.production.json but I would like Ghost to run in production mode. The background is that I wish to launch many copies of Ghost on different ports. So, like,
mktemp current/core/server/config/env/config.XXXXXX.json
cp current/core/server/config/env/config.production.json current/core/server/config/env/config.XXXXXX.json
edit the port number and then
NODE_ENV=XXXXXX node current/index.js
I noticed that, if NODE_ENV=<something_other_than_production> the server performs much more poorly than when NODE_ENV=production, even though the config file current/core/server/config/env/config.XXXXXX.json has the exact same content (save, maybe for the port) than current/core/server/config/env/config.production.json
Would it be possible to add a key to the configuration file, like, maybe { “server”: { “mode”: “production” } } so the server goes into production mode even though the NODE_ENV is set to XXXXXX?