←back to thread

Phoenix.new – Remote AI Runtime for Phoenix

(fly.io)
638 points wut42 | 4 comments | 20 Jun 25 14:57 UTC | HN request time: 0.807s | source
Show context
chrismccord ◴[20 Jun 25 15:54 UTC] No.44328933[source]▶
Phoenix creator here. I'm happy to answer any questions about this! Also worth noting that phoenix.new is a global Elixir cluster that spans the planet. If you sign up in Australia, you get an IDE and agent placed in Sydney.
replies(21): >>44329010 #>>44329145 #>>44329199 #>>44329447 #>>44329669 #>>44329679 #>>44329692 #>>44329699 #>>44329766 #>>44330059 #>>44330099 #>>44330127 #>>44330670 #>>44331525 #>>44331688 #>>44334922 #>>44335271 #>>44336137 #>>44336958 #>>44337485 #>>44344757 #
1. mrdoops ◴[20 Jun 25 17:00 UTC] No.44329699[source]▶
Any takeaways on using Fly APIs for provisioning isolated environments? I'm looking into doing something similar to Phoenix.new but for a low-code server-less workflow system.
replies(1): >>44329773 #
2. chrismccord ◴[20 Jun 25 17:08 UTC] No.44329773[source]▶
1 week of work to go from local-only to fly provisioned IDE machines with all the proxying. fly-replay is the unsung hero in this case, that's how we can route the *.phx.run urls to your running dev servers, how we proxy `git push` to phoenix.new to your IDE's git server, and how we frame your app preview within the IDE in a way that works with Safari (cross origin websocket iframes are a no go). We're also doing a bunch of other neat tricks involving object storage, which we'll write about at some point. Feel free to reach out in slack/email if you want to chat more.
replies(2): >>44329924 #>>44347952 #
3. mrdoops ◴[20 Jun 25 17:28 UTC] No.44329924[source]▶
Thanks, I might hit you up when I'm in the weeds of that feature.
4. randito ◴[22 Jun 25 15:58 UTC] No.44347952[source]▶
Would love to read about some of the techniques for how you accomplished this.