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

Adds heroku deployment workflow for rails app only #6

Merged
merged 2 commits into from
May 20, 2015

Conversation

nbantatua
Copy link
Contributor

No description provided.

####After all this...
...why not add `rail_12factor` gem to Gemfile? *If you're not concerned with Rails logs being written to file, `config.serve_static_assets = true` is all you need.*

...I use `secrets.yml` instead of `application.yml`? *It's a known limitation for using Heroku. Best stick in using `ENV[___]` approach on this one.*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# secrets.yml
production:
  secret_key_base: <%= ENV['SECRET_KEY_BASE'] || '...' %>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rstacruz that is also a cool approach, but we really have to agree on the most foolproof approach in handling credentials. So far we use secrets.yml the same manner as application.yml, we do not checkin these files into repo(adding them at .gitignore).

Should we instead:

  • Check in secrets.yml as part of the repo.
  • Use application.yml as well, but not included in repo
  • All sensitive credentials set from application.yml are to be set from secrets.yml
  • Use Rails.application.secrets in calling these credentials
  • Refrain from using ENV[]

rstacruz added a commit that referenced this pull request May 20, 2015
Adds heroku deployment workflow for rails app only
@rstacruz rstacruz merged commit 055cb33 into master May 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants