vschroeder
Hello there, I tried to find an answer for this question but couldn’t find it anywhere, so here it goes!
We have a project composed by some docker images, one of them containing an Elixir application inside. During development, Mix and all the test tooling is made available for the developer. In production, a minimal image is deployed containing just the release (BTW, releases are a killer feature of Elixir/Erlang, I love it!)
Now we have dependency on a file (which happens to be a certificate) that has to be mounted during development (the certificate gets always rotated, for testing purposes) and has to made available to the release in production, either shipped with the container image or mounted by another mechanism at a known and predefined (or configurable) location.
So, the question: is there any recommended way to make this kind of static file-based asset available to the Elixir (or Erlang) runtime? Where should static assets be placed? I’m aware that I can put it pretty much anywhere I want, but is there any good practice to be followed, among the other directories like lib, deps, etc?
Thanks in advance!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ai
- #elixirconf-us
- #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.
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
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 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ityonemo
I typically use priv/assets. Erlang comes with
:application.priv_dir/1I think? (I’m on my phone so can’t check) which will accurately track it through releases.Nicd
Yep use
priv, it’s built into the release by default. Then you can use:code.priv_dir(:your_app)orApplication.app_dir(:your_app, "priv")to get its path, which will work in both development and release. Of course, it won’t help if you want your file to be placed after you build the release (in which case you could place it in the directory manually but you could put it anywhere else in the filesystem too and it’s up to you).egze
There are also
Overlaysformix release. Maybe it can also help.ityonemo
thanks for the correction! I knew my memory was fishy.
vschroeder
Thanks for all the suggestions. This was waaaay more useful than I was expecting! Both solutions (
privdirectory and releaseOverlays) sound really solid. I’ll try them both and follow up this thread with what worked the best.