Conversation
ghost
assigned
| @@ -1,4 +1,16 @@ | |||
| Rails.application.configure do | |||
|
|
|||
There was a problem hiding this comment.
@s-espinosa @icorson3
I think this might be set up right, but I'm not sure.
|
|
||
| # Do not fallback to assets pipeline if a precompiled asset is missed. | ||
| config.assets.compile = false | ||
| config.assets.compile = true |
There was a problem hiding this comment.
@s-espinosa @icorson3 I see a lot of conflicting information about setting this to true or false
BLaurenB
left a comment
BLaurenB
left a comment
There was a problem hiding this comment.
Sorry if I used callouts too much, I thought it'd be easier to point you to my questions.
|
|
||
| # Environmental secrets are only available for that specific environment. | ||
|
|
||
| development: |
There was a problem hiding this comment.
@s-espinosa @icorson3 I tried to remove this, but for some reason it still got pushed to GH?
config/secrets.yml
Outdated
|
|
||
| production: | ||
| secret_key_base: <%= ENV["SECRET_KEY_BASE"] %> | ||
| secret_key_base: <%= Figaro.env.secret_key_base %> |
There was a problem hiding this comment.
@s-espinosa @icorson3
I think this is correct, but I'm not sure how to input the AWS variables that heroku needs. Or they might not need to be saved here because I'm also setting them using terminal commands heroku config AWS_THINGY=random5stuff3
2 participants
@s-espinosa
@icorson3
I'm getting really confused, and my teammates really want me to reach out to you for help. I have been trying to do it myself using docs and other resources.
I am really confused about what to put in various files for using Figaro, Paperclip, and Heroku all together. I don't think other classmates are using figaro. Even though I tried to get things set up correctly, I still ended up pushing my AWS keys and secret keys to GitHub last night.
This is a master version that doesn't have full functionality but I've been working on it to get paperclip working. Paperclip was working on localhost, but I couldn't get it to work via heroku.