hakarabakara
I am running elixir version 1.10.4 on Centos 7 and having trouble with runtime.exs fetching environment variables configured in the systemd service.
The same setup works on Ubuntu 20.04 but running elixir 1.11.4.
My assumption was runtime.exs was introduced in version 1.10.* and should therefore work? If so, what other option do I have because the values are defined in a systemd service that looks like this:
[Unit]
Description=My Service
After=network.target
StartLimitIntervalSec=0
[Service]
Type=simple
EnvironmentFile=/etc/systemd/system/myservice.conf
ExecStart=/home/applicationuser/myservice/prod/rel/myservice/bin/myservice start
ExecStop=/home/applicationuser/myservice/prod/rel/myservice/bin/myservice stop
Restart=on-failure
User=applicationuser
StartLimitIntervalSec=45
[Install]
WantedBy=multi-user.target
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 3 of 3 Posts
hakarabakara
I just read the documentation, my fear was that the environment variables would not be detected at compile time, I don’t know why I assumed they won’t be read from releases.exs.
Nicd
Can you clarify this a bit? What is the specific issue you are having? Are the environment variables not being read? At compile or runtime?
runtime.exswas introduced in 1.11,releases.exsexists in 1.10. You mentioned both, which one are you using?Note that
runtime.exswill be evaluated in a development environment also, whereasreleases.exswill only be evaluated when running a release.hakarabakara
Thank you for your response and apologies for responding late.
I was using
runtime.exshaving forgotten it was introduced in 1.11 and not in 1.10 so was pulling my hair as to why the configurations were not being read at application start.Moving the configuration to
releases.exskind of worked, I have specified application port as4000but it runs on16392which I was not going to investigate yet because of a deadline