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
{{ message }}
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
We're looking to combine a standard eb.yml file with an application specific config but there's no way to do so in the current code.
Would you be open to changing the config task to look at an ENV variable for the path to the config?
We're thinking about something like this:
config_file=ENV['EB_CONFIG'] || 'eb.yml'# load the configuration from same dir (for standalone CI purposes) or from the rails config dir if within the rails projectfilename=EbConfig.resolve_path(config_file)unlessFile.exists?filenamefilename=EbConfig.resolve_path('config/' + config_file)endEbConfig.load!(environment,filename)
The text was updated successfully, but these errors were encountered:
Instead of altering the code, we're considering not checking in our eb.yml file and specifying an app_eb.yml file which would be checked in. We can then have a rake task that runs before eb:config to generate the eb.yml file.
Just adding these details to see how you might want to address this because others may want to do the same and may have difficulty without an elastic-beanstalk specified way to handle this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're looking to combine a standard eb.yml file with an application specific config but there's no way to do so in the current code.
Would you be open to changing the config task to look at an ENV variable for the path to the config?
We're thinking about something like this:
The text was updated successfully, but these errors were encountered: