You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want my config/initializers/copycopter.rb to look like this:
CopycopterClient.configure do |config|
config.api_key = ENV['COPYCOPTER_API_KEY']
end
In this particular instance, the reason is because I want to use Copycopter in an app that will soon be open sourced. However, I think it's cleaner in general to think in terms of having config variables as separate from the source code. Heroku provides them and you can use them locally with foreman in the .env file. However, the two cases that .env or config variables aren't available are in the test suite and during rake assets:precompile when deploying to Heroku. It'd be sweet if Copycopter just printed a warning instead of throwing an error, which blows up the deploy and makes for an unsatisfying end to a test run.
The text was updated successfully, but these errors were encountered:
It's now possible to use ENV variables in Copycopter's config on Heroku. So, Copycopter is usable on Heroku except for the rake task, which still throws this error.
It also throws the error on every rails generate task and other items.
I would like to replace this error with a printed warning. Thoughts?
I want my
config/initializers/copycopter.rb
to look like this:In this particular instance, the reason is because I want to use Copycopter in an app that will soon be open sourced. However, I think it's cleaner in general to think in terms of having config variables as separate from the source code. Heroku provides them and you can use them locally with foreman in the
.env
file. However, the two cases that.env
or config variables aren't available are in the test suite and duringrake assets:precompile
when deploying to Heroku. It'd be sweet if Copycopter just printed a warning instead of throwing an error, which blows up the deploy and makes for an unsatisfying end to a test run.The text was updated successfully, but these errors were encountered: