zoedsoupe
I’m following these two tutorials:
https://thoughtbot.com/blog/deploying-elixir-to-aws-elastic-beanstalk-with-docker
And I can create a release without so much effort, however, creating a .env file and then sourcing it doesn’t get effect…
My solution was to declare each env var manually, on one-line shot and run migrations and start the app.
Am I doing something wrong?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zoedsoupe
If you get here from google, I strongly advise you to read the entire topic! You’ll learn a lot!
Yeah! Rolling back to another branch solved the test issues…
So summing up:
env var not matter on creating a release with
MIX_ENV=prod mix releasethey only matter on starting the release!
Thank you all so much!
Also Liked
NobbZ
It is not that easy. Depending on how and where you read them they might also affect the build.
config/runtime.exsis only evaluated during application boot, therefore its solely runtime config.NobbZ
What is
DB_URLin the system environment?Do you perhaps have no dockerignore file which contains
_buildanddepsand therefore partial builds slip into your container, which again might cause config values to exist that you do not want to exist?NobbZ
As far as I know,
config/test.exsdoes not set or overwrite thesecret_key_basein a default generated application.So you might have changed some things for a reason or by accident. It does not make (much) sense to read the env during test. If you do not want to hardcode a
secret_key_baseinconfig/config.exs(which is still there) you can remove it there and useconfig/runtime.exsinstead to read it from the env, while hardcoding some “well known secret” inconfig/test.exs.Or you just don’t touch the value in the test config and use the one from the “main” config as a well known default, that you shouldn’t use in production then though.