I like Elixir...but sheesh you have to read 2 more full medium articles before you even see any code. I mean the linked article basically explains how to setup an s3 bucket with appropriate permissions.
Couldn't you just use arc (with arc_ecto if you're using ecto)? Arc is basically the Elixir version of Rails' Paperclip, which does all of the heavy lifting for you.
It's a lot easier to bootstrap the backend-style. Even in client-side world you still have to do plenty in the backend to manage knowledge of the existence of said images.
Thanks for the tutorial.
Image upload handling is a tricky task. Beyond storage, we’ve found that being able to moderate and filter out bad images was a huge pain point.
For anybody experiencing the same challenges, I would suggest using https://sightengine.com — a realtime image moderation API based on Deep Learning
Except you have to be careful with symbols in Elixir. They don't get cleaned up until a crash. That means in things like Phoenix you aren't supposed to use symbols as parameter maps in your controllers as a user could easily blow up your memory by making tons o' calls.
EDIT: I would also add that they are the preferred key for Maps when using internal Map structures (ones that you have complete control over and users don't)
That's a "problem" with the erlang vm actually, you have a limit number of allowed atoms (I think 2 million). When receiving user input, you should not let users create arbitrary atoms because this would allow a atom exhaustion attack.
In these cases, what we do is assing a "string" map, something like :input["arbitrary_key"]
ETA: default is 1 million atoms actually. It can be increased but it's usually a smell/something to be investigated.
