An observation here. There was a post a little while ago about sensible infrastructure defaults:
and another post popped up today ‘how do I deploy to production’
It occurs to me that the setup decisions in ‘rails new’ are closely related to the production deployment requirements.
In terms of deployment, I wondered (elsewhere) whether Rails could abstract the requirements in such a way that different ‘production gems’ could take over. - If I want to run on Heroku, I add just gem 'HerokuInfrastructure' if I want to run on Hatchbox, it is gem 'HatchboxInfrastructure'
It may be that this is a good filter to use when thinking about the saved config from an install.config file (however that may be managed). Could the install config file be the same file that provides all the info a deployment gem requires??
certainly, a lot of the questions asked in install will provide the answers that a deployment solution needs to know:
database / redis / active storage / etc
obviously some might have different answers; sqlite in dev vs postgres in production (though I’m a fan of keeping dev/testing as close to production as reasonable)
anyway - my point is that making first-install friendly/flexible may be closely related to the question of making deployment friendly/flexible. It may help to keep both in mind as the first is tackled…
thanks.