Skip to content

Heroku Compatibility #84

Open
Open

Description

@jamesy829

I use the suggested guide to setup usage of env variables on Heroku

https://github.com/railsconfig/rails_config#working-with-heroku

I have my env variables on Heroku as following:

Settings.database.dbname: value
Settings.keys.aws_access_key_id: value
Settings.keys.aws_secret_access_key: value
Settings.keys.devise_secret_key: value
Settings.keys.directory: value
Settings.keys.region: value
Settings.keys.secret_key_base: value

I noticed that when it tries to run rake task, it would complain env variables not found, and doing some digging, I discovered those are not valid env variables and Rails would not pick them up properly.

I have pushed those env variables using the rake task provided bundle exec rake rails_config:heroku

Is this a valid bug or the expected behaviour? If its not a bug, what's the approach I should be taking.

Thanks in advance.

Activity

  1. jamesy829 commented on Jul 30, 2014

    @jamesy829
    Author

    Found a possible work around

    https://github.com/finnlabs/rails_config-env_source

    Giving it a shot and if works, submit a PR to merge

  2. jamesy829 commented on Jul 31, 2014

    @jamesy829
    Author

    I have confirmed using this and the specified format of environment variables will allow the deployment to Heroku work properly, would be nice to have this as part of this gem

  3. fredwu commented on Aug 6, 2015

    @fredwu
    Member

    Great work! Any chance of submitting a PR? :)

  4. added this to the 1.3 milestone on May 12, 2016
  5. modified the milestones: 1.4, 1.6.0 on Oct 23, 2017
  6. modified the milestones: 1.6.0, 1.6.1, on Nov 3, 2017
  7. modified the milestones: 1.7.0, 1.7.1 on Feb 9, 2018
  8. removed this from the 1.7.1 milestone on Jun 19, 2019
  9. pkuczynski commented on Dec 9, 2020

    @pkuczynski
    Member

    @cjlarose do you think it makes sense to add any of this to our source code?

  10. cjlarose commented on Dec 9, 2020

    @cjlarose
    Member

    I'll take a look. It's an old issue, so this might already be fixed, but we can at least improve our docs with recommendations.

  11. self-assigned this
    on Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions