James_E
I have a mix app, and the following snippet in runtime.exs:
if config_env() == :prod do
# ...
phx_ip = case System.get_env("PHX_IP", "ANY") do
"ANY" -> :any
s -> case MyApp.Util.parse_ip(s) do
{:ok, ip} -> ip
{:error, error} -> :erlang.error(error)
end
end
However, when I try to port this snippet to dev.exs (we need to test the specific-IP handling code in dev), it won’t compile because MyApp.Util isn’t available.
How should I make a module of my code available to dev.exs?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #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.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
This is not an answer to your question, but it’s perfectly fine to gate code by env in
runtime.exs; this is in fact exactly what theif config_env() == :prod doline in your snippet does.(You are probably aware of this, but I mention it just in case.)
seeplusplus
This may be similar to this thread,
But based on some quick testing I’d say you don’t really want to do what you’re doing inside a
dev.exs. It’s only run before compile (which is why you can’t read your modules’ functions) and is not run after you’ve built your release. In your case it looks like you’re reading an env var to determine which IPs to bind to, which is definitely something you’d want to do on each startup.Could you just remove the
if config_env() == :prodaround yourphx_ipcode to test in dev?adamu
Any code that needs to be tested should be in a module, not in a config file.
hauleth
You cannot use functions defined in your code in
dev.exsas there you define compile-time config. So you will have chicken-egg problem if that would be possible.