t.t
hello,
i’m using base64 to encode/decode attachments. the encode64 worked fine but the decode returns a binary text and I’m having trouble converting it back to the original attachment.
Base.decode64!() response:
<<137, 80, 78, 71, 13, 10, 26, 10, 0, 0, ...>>
can anyone help?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 10 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Well there’s your problem.
File.writedoes not do downloads. It writes bytes to a filesystem.It looks like you’re trying to to serve files to the users of your project. Take a look at
waffleandwaffle_ectoas a start.APB9785
File.write/3is not a pure function. It returns:okbut if you look on the filesystem, you will see the file has been created as a side-effect. Then it is up to you how you serve that file to your users - that is an entirely separate issue.t.t
the file.write returns :ok and I can see the file open inside my project. but it needs to be available to download when someone calls the endpoint.
t.t
I want to download the decoded file, I’m not being able to do that with File.write()
dimitarvp
Can you give your use-case in more details?
Sounds like you’re trying to get the contents of the
Content-DispositionHTTP header. You got no problems withFile.writeitself; that one looks to work fine for you.APB9785
The first argument of
File.write/3is where you choose the output file path. It can be anything you want it to be.t.t
because I want the return to be what’s on the “pathOnClient” when the upload was made. so I want it to be “test.png”. Is that possible?
APB9785
If it returns
:ok, then the file write was a success. What’s the problem?t.t
pathOnClient = “test.png”
version: = the pathOnClient file encoded in base 64
then, I have to decode that file as show it the same way as it was uploaded, like the “pathOnClient” shows. I’ve done tests with File.write() but it returns :ok only.
APB9785
File - write/3 can write a binary to a file