Initialize dotenv vars correctly in debian, simplify conf #193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tkwidmer would be nice to get this checked on OSX an merged in, as the build is currently broken on (at least) debian. |
|
wont this override the production env variable set in heroku? |
|
Thats why we had test and development secret keys set. and didnt set just a general env variable. |
|
@tkwidmer the dotenv gem is only bundled in the test and development environments, so it shouldn't be an issue on Heroku. |
|
k, wanted to make sure |
tkwidmer
added a commit
that referenced
this pull request
Jan 30, 2015
Initialize dotenv vars correctly in debian, simplify conf
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes #170 on Debian at least.