As @LostKobrakai pointed out, mix assets.deploy just processes js/css from assets folder.

Rest of the images, svgs, icons, robots.txt, canary.txt, ads.txt, favicon, etc, you need to place them directly priv/static folder.

I guess, it just minifies, compresses and generates file hash on js/css files.

However the images are compressed by us, so they are directly placed in priv/static folder and the mix assets.deploy works on those images in place:

Screenshot 2022-11-08 at 3.46.44 PM857×761 33.5 KB

Excerpt from Introduction to Deployment:

This step is required only if you have compilable assets like JavaScript and stylesheets. By default, Phoenix uses esbuild but everything is encapsulated in a single mix assets.deploy task defined in your mix.exs.

And that is it! The Mix task by default builds the assets and then generates digests with a cache manifest file so Phoenix can quickly serve assets in production.

P.S. I fumbled in the beginning as well, but I just saw existing projects by other people and figured out that you just leave images and such in priv/static folder.

Yup, it’s a good practice.

Let me find an official documentation.

As @LostKobrakai mentioned, it’s a new way of doing it after webpack was removed!

Note running mix phx.digestwill create digested files for all of the assets in priv/static , so your images and fonts are still cache-busted.

https://hexdocs.pm/phoenix/1.6.1/asset_management.html#images-fonts-and-external-files