The most idiomatic and most reliable and only correct way is to use :code.priv_dir/1.

Example of use in an attribute (compile time resolution) - also works in a release (haven’t tested moving the release to another dir (I’m working with docker (alpine-elixir)) - if you’re going to do that - you’ll probably want to make it a function instead.

https://github.com/bryanhuntesl/ex_bench/blob/fe5bfea7ab7b71dcdb0984aa0e445a8c6fcacd7d/lib/ex_bench.ex#L3

In elixir I feel Application.app_dir/2 is more ideomatic.

No, compile time resolution will only work by accident, please resolve at runtime, it’s fast enough.

I checked your code, and in theory it will only ever work when you run the release from a machine that still has the source folder available at it’s original location.

Oh, since when is that there? I should try to remember that one.

Edit

I read the docs, it does not necessarily point to something that contains the priv folder… It points to where the compiled modules will be… Or I’m missinterpreting the docs… I’d stick to :code.priv_dir.

If you do Application.app_dir(:myapp, "priv/static/file.ext") it’ll work. It surely isn’t the same as :code.priv_dir as it’s always starting at the parent of the priv dir, but it works. E.g. Plug.Static is using it.

Thank you both!

I’ve noticed that neither Application.app_dir/2 not :code.priv_dir/1 seem to work in config files, since the app does not exist yet. Is there any way around this?

Configure only the path and feed it to those functions as runtime.

How to do this?

# in config
config :my_app, path: "…"

# in your code
rel = Application.fetch_env!(:my_app, :path)
path = Application.app_dir(:my_app, path)