ostap
I’m building a file converter website which does not require an account. It stores all conversions in the database and assigns owned conversions to a session as a list of IDs.
I don’t use S3 yet, so all converted files are stored in a priv/static/uploads.
defmodule MyAppWeb do
def static_paths, do: ~w(uploads
These files are mostly stored temporarily and deleted after 24 hours. But there would be the case when we store them longer if someone makes an account.
Is it acceptable to keep these files publicly exposed? Is it better to somehow authenticate access to these files? If so, is there an easy way to do so with Plug/Phoenix?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
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.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
You can just use authentication plug for the static files?
The way I did it back in the day is that I would have a dedicated controller that would serve the files based on the authenticated user, as most probably you won’t want authenticated users to see each-other’s files.
ostap
Thank you! A dedicated controller for serving files seems to be what I want. I can also make it domain-specific so that it fetches the database record and checks the ownership to then decide whether to serve the file.
I now think my file-serving controller could benefit from utilizing Nginx’s
X-Accel-Redirectheader to send over large files.garrison
You could give each file an unguessable “token” and allow download via that token. Depending on your use case this could be handy for allowing a user to send the download link to someone else (or another computer).
If a logged-in user wants a truly “private” (authenticated) upload then you could make the token optional in the schema (or better, a “visibility” field) and authenticate accordingly.