Skip to content
This repository was archived by the owner on Jun 13, 2019. It is now read-only.

Can run with custom Mix.env, not just prod. #30

Merged
merged 1 commit into from
Apr 27, 2017
Merged

Conversation

cstar
Copy link
Contributor

@cstar cstar commented Apr 26, 2017

No description provided.

@cstar
Copy link
Contributor Author

cstar commented Apr 26, 2017

Not ready yet, MIX_ENV has to be explicitly passed on the CLI.

@teamon teamon merged commit d393e1d into Recruitee:master Apr 27, 2017
@teamon
Copy link
Contributor

teamon commented Apr 27, 2017

Ahh, I saw the tiny code change and merged right away, but then I've noticed the last comment.
@cstar in current form, will it break the prod build or is it that it's just always be prod?

@cstar
Copy link
Contributor Author

cstar commented Apr 27, 2017

it will break the build — it will use "prod" for docker.build and "dev" for docker.release as Mix.env.
Results in failure, unless you explicitly specify MIX_ENV in CLI

@teamon
Copy link
Contributor

teamon commented Jun 23, 2017

I have reverted this change - will continue with #40

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants