aboutsummaryrefslogtreecommitdiffstats
path: root/actionview/lib/action_view/context.rb
diff options
context:
space:
mode:
authorBen Thorner <ben.thorner@digital.cabinet-office.gov.uk>2019-06-10 16:46:52 +0100
committerBen Thorner <ben.thorner@digital.cabinet-office.gov.uk>2019-06-19 14:06:38 +0100
commit2e5ec9a6efc80fd266b974fc50b2775afa73130b (patch)
treede6d7f3de52367b6836d18d86ad1003ea4772f22 /actionview/lib/action_view/context.rb
parentc2847716913d3fb72fd423009be1d4f124e4aa94 (diff)
downloadrails-2e5ec9a6efc80fd266b974fc50b2775afa73130b.tar.gz
rails-2e5ec9a6efc80fd266b974fc50b2775afa73130b.tar.bz2
rails-2e5ec9a6efc80fd266b974fc50b2775afa73130b.zip
Allow using env var to specify pidfile
Previously it was only possible to specify the location of the pidfile for the 'rails server' command with the '-P' flag. This adds support for specifying the pidfile using a PIDFILE env var, which can still be overridden by the '-P' flag and with the default pidfile path unchanged. The motivation for this feature comes from using Docker to run multiple instances of the same rails app. When developing a rails app with Docker, it's common to bind-mount the rails root directory in the running container, so that changes to files are shared between the container and the host. However, this doesn't work so well with the pidfile and it's necessary to (remember to) add a '-P' flag to the 'rails server' command line; being able to specify this flag using an env var would make developing with Rails+Docker a bit simpler.
Diffstat (limited to 'actionview/lib/action_view/context.rb')
0 files changed, 0 insertions, 0 deletions