thojanssens1
Let’s say I configure some of the assets (user uploads) to be served at /uploads:
plug Plug.Static,
at: "/uploads",
from: {:my_app, Application.fetch_env!(:my_app, :uploads_directory)}
plug Plug.Static,
at: "/",
from: :my_app
only: ~w(css fonts images js favicon.ico robots.txt)
How do I create img elements (for those user uploads) using that configuration? I guess there is a way to not hardcode “/uploads” for all the src attributes for the uploads?
Imagine I change the :at path from “/uploads” to something else, if I hardcoded “/uploads” in my img elements, I would have a huge application-wide refactor.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
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
- #metaprogramming
- #hex
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!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Wrap whatever you do with the paths of files in a function and use that function.
thojanssens1
It’s a pity that this plug doesn’t take a param like “name” (which I would set e.g. to “upload”), then in the view I could write something like:
And the src path will be prefixed by the path configured in the Plug (
:at).Ofc I could write that function myself (this is what you suggested if I understood correctly). But I think something like that could be included be default.
LostKobrakai
Plug.Staticcannot do that. There’s no concept of route generation in plug at all. Phoenix does add that as part of its endpoint and router, but afaikstatic_pathis not aware ofPlug.Static. It just creates paths relative to your endpoint’s root. And that root can even be moutned in a folder as well, e.g. atmydomain.com/some/folder/. Theconnstruct might never be aware of that when mounted behind a reverse proxy and the/some/folderpart might only configured as part ofMyApp.Endpoint’s configuration.thojanssens1
Well there’s always a way to make things happen:D I think that there should be something on top of Plug Static that allows to generate paths based on the options given to Plug Static. In lack of that, in every project I’ll have to create helper functions in order to reflect these configurations in the views for the paths to the concerned assets.