Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add puma configuration to version control #3850

Merged
merged 4 commits into from
Nov 14, 2019
Merged

Add puma configuration to version control #3850

merged 4 commits into from
Nov 14, 2019

Conversation

javierm
Copy link
Member

@javierm javierm commented Nov 12, 2019

References

Objectives

  • Make it easier to track changes to puma configuration files

@javierm javierm self-assigned this Nov 12, 2019
config/puma/staging.rb Outdated Show resolved Hide resolved
config/puma/production.rb Outdated Show resolved Hide resolved
config/puma/preproduction.rb Outdated Show resolved Hide resolved
These files are only loaded when the stage already has the value set
inside them, so we don't need to set it again.

On the other hand, the `rails_env` setting is configured in the
`config/deploy.rb` file.
Deploy environment files were loaded after config/deploy.rb was loaded,
meaning if we used settings like `deploy_to` or `current_path` to set
variables inside the config/deploy.rb file, we'd be using the default
settings instead of the ones dictated by the deploy environment files.
@javierm javierm force-pushed the puma_rb branch 2 times, most recently from 765c138 to dd76f41 Compare November 13, 2019 12:12
We were using Capistrano's shared folder because it was the default
folder used by the capistrano-puma gem. However, it's easier to manage
it if it's under version control.

So we're moving the old `puma.rb` to `puma/development.rb`, and we use
the new `puma.rb` file for all environments except development. Anyone
installing CONSUL can change these files at will or change the specific
files for preproduction, production and staging environments.
@javierm javierm merged commit 8ead74c into master Nov 14, 2019
@javierm javierm deleted the puma_rb branch November 14, 2019 12:31
smarques pushed a commit to venetochevogliamo/consul that referenced this pull request Apr 29, 2020
Add puma configuration to version control
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants