Majd
Hi, I’m building a REST API using Phoenix, We have a product schema that is related to many images.
We first started thinking more about image uploading while developing the product APIs, we firstly wanted to do a basic multipart upload along with the product data, with leveraging Waffle and ecto to upload to an S3 compatible storage.
However, we were a bit influenced by Phoenix’s LiveView way of handling uploads. Briefly, it uploads files to a tmp location before submitting the other data in the form. It leverages a GenServer that deletes those files if not consumed by the LiveView. This way however, also leverages that the LiveView is an active socket, and all the data needed about files, locations can be communicated through the socket.
And finally, my question is, do you guys recommend replicating this method of uploading images in a JSON API Phoenix app? Given that the primary consumer of this API is a mobile app, and if done, we’ll be mostly be leveraging long polling to maintain a connection with the server and speaking with the GenServer that’ll delete our temp files if not consumed.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #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.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tfwright
If you are uploading to S3, I would recommend uploading directly there in the client, and then having the client send just the metadata to your API. On the server, you can handle “promoting” the file on S3 as part of a scheduled/async task.