deploy.config section of your boxfile.yml allows you to customize deploy process.
Once your app is in production, environment variables like where and how to connect to data services are available. If your app can't use environment variables, you can define commands that will inject these values into your static configuration files. These commands will be run just before your web/worker is started.
Additionally, you might also use this phase to shift configuration around for running in production.
deploy.config: transform: - 'sed -i /HOST/$DATA_DB_HOST/g config/database.xml' - 'if [ "$ENV" = "prod" ]; then mv config-prod.yml config.yml; fi'
Before & After Live Hooks
Deploy hooks allow you to run commands before and after new web or worker instances begin accepting live requests. These are covered in detail in the Build & Deploy Hooks doc.
In short, you can define hooks to migrate data, prime cache, or run any administrative task automatically on deploy.
deploy.config: # run command on any one instance of web.main component before activation before_live: web.main: - 'bundle exec rake clear-cache' # run command on all instances of web.main component before activation before_live_all: web.main: - 'bundle exec rake register-nodes' # run command on any one instance of web.main component after activation after_live: worker.mail: - 'bundle exec rake prime-cache' # run command on all instances of web.main component after activation after_live_all: worker.mail: - 'bundle exec rake prime-local-cache'
Reach out to firstname.lastname@example.org and we'll try to help.