andreamancuso
Hey folks,
This might sound niche, but I think it’s worth bringing up - especially given Phoenix’s reputation for being lightweight, portable, and fast.
I recently attempted to run a full Phoenix + LiveView stack on a RISC-V board (specifically a Milk-V Mars running Debian Trixie). Everything worked surprisingly well:
- Erlang/OTP installed and ran without a hitch
- Elixir compiled fine
- Phoenix booted up like a champ
- Even Docker worked!
And then… Tailwind happened.
As most of you know, Phoenix uses the Tailwind CLI during asset compilation - and unfortunately, the Tailwind CLI doesn’t currently provide builds for RISC-V. Even compiling it from source doesn’t work cleanly out of the box due to its Rust-based binary and tight coupling with unsupported system assumptions (like filesystem access during runtime scanning in v4).
This is the roadblock stopping Phoenix from running cleanly on RISC-V systems out of the box - and frankly, it’s a shame. Everything else is ready. We’re just blocked by one missing binary.
I’d like to suggest that the Phoenix core team officially reach out to Tailwind Labs, asking them to consider adding a RISC-V target for their standalone CLI releases.
It would:
- Unlock Phoenix development on new/emerging architectures
- Encourage broader experimentation (edge computing, low-power setups, alt-arch servers, etc.)
- Future-proof the asset pipeline for what’s quickly becoming a real-world dev target (Debian officially supports RISC-V)
I know this is an upstream request, but coming from Phoenix - a major Tailwind integrator - it might carry more weight than individuals asking piecemeal.
Just planting the seed.
Thanks for considering and apologies if anyone finds this proposal silly/outrageous.
Andrea
Where Next?
Trending in Proposals: Ideas
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Develop your skills with books, videos, and courses.
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 4- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
arcanemachine
I agree. I got a Phoenix application running on a Scaleway RISC-V VPS a year ago, and it went pretty well. I had to open a pull request to get esbuild working. (IIRC it works with a certain set of hardcoded architectures, and I just had to add RISC-V to the list).
I tried to build the standalone Tailwind CLI package but there was some upstream dependency that was blocking my progress. I’m unfamiliar with that build toolchain and it was a pain.
You can imagine my delight when I went to pull up the GitHub discussion I started a year ago… and the only reply is from you, 3 hours ago. LMAO
I think if we make enough noise about it, we could probably get something going on that front. Or at least irritate some busy developers on the Internet.
I would check to see if any progress has been made towards getting
turboworking with RISC-V. See if you can build Tailwind CLI locally, then work your way from there.andreamancuso
LOL, sorry for giving you false hope.
I compiled turbo (by vercel) on my Milk-V Mars, took 2+ hours. It’s 03:18am as I type this so will try compiling tailwind tomorrow. That said, I was able to compile the oxide binary. Let’s see what happens.
arcanemachine
I vibe-coded a wrapper that makes it so that vanilla Phoenix can work on RISC-V with Tailwind support:
FWIW it’s a workaround, not a proper solution (Bun doesn’t support RISC-V, which is a hard blocker for official
tailwindcssCLI support), but it does the job.Just figured I’d let you know since you’re the only other person I know who has dug into the issue.
P.S. This page is currently the top result on Google when you search
tailwind risc-vandreamancuso
This is excellent, thank you for letting me know!