afternow
Hello
I in my umbrella I have an app with Phoenix 1.4.3. The App is setup with webpack and VUE JS (placed under assets/src). Everything work so far, but if I pack everything to a release (using Distillery), it doesn’t work anymore. It seems that the whole VUE stuff will not load. Before I create the release, I run “mix phx.digest”, but It seems it doesn’t work properly. When I delete everything in “priv/static” and run then the Digest command, it only creates a cache_manifest.json file with content “{“digests”:{},“latest”:{},“version”:1}”
I’ve read the documentation here mix phx.digest — Phoenix v1.8.8, but it didn’t helped me.
Is there anything else I have to consider?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
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
- #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
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
mix phx.digestdoesn’t retrieve files from anywhere by default, but just act’s on what’s inpriv/static/already. Basically you’re in charge of getting the needed files intopriv/static/, but the default assets pipeline generated by phoenix does include code to ensure the compiled js/css/images will be copied there. This makes it seem like phoenix is copying the files, while it’s actually just a certain webpack configuration doing that, while everything else assumes stuff is inpriv/static/. Everything withinpriv/should automatically be included in distillery releases.afternow
Thank you LastKobrakai for your answer. This helped me a lot!
For the deployment I run npm run deploy in the assets folder. This runs webpack and copy the data into the priv folder. Then mix phx.digest and finally mix release