-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix config file locations and clean up test warnings #217
Conversation
d1ceee6
to
93caa66
Compare
config/config.exs
Outdated
@@ -1,4 +1,4 @@ | |||
# This file is responsible for configuring your application | |||
# and its dependencies with the aid of the Mix.Config module. | |||
use Mix.Config | |||
import_config "#{Mix.env}.exs" | |||
import_config "deploy/#{Mix.env}.exs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this line just be removed? At least it seems a bit confusing to import "deploy" config into the Bootleg config 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch @pmeinhardt 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once the config correction is in this'll look good 👍
Docker is giving me the business right now when i'm running the tests to verify that the cleanup of the config is kosher, hopefully resolved soon. @pmeinhardt is correct. it turns out this appears to be just cruft from the very early version of bootleg. deploy config files no longer need to be explicitly imported, as they are loaded automatically now when |
93caa66
to
cc71db6
Compare
Ok, all ready @rjanja |
This fixes the issue that @pmeinhardt noted after he reworked/fixed the
IO
verbosity