Phoenix.new – Remote AI Runtime for Phoenix

Post by randito » Sun, Jun 22, 2025, 3:58 PM UTC

chrismccord wrote: post #71

mrdoops wrote: post #67

Earlier quoted context omitted.

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.

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 b…

Post by lawn » Sun, Jun 22, 2025, 5:52 PM UTC

poisonta wrote: post #262

Phoenix needs an ActiveRecord-like database abstraction layer. Many Rails developers try Phoenix at some point because they may need better performance. They’re so accustomed to the Rails structure that they assume Rails has done everything right. However, Ecto and ActiveRecord are two very different beasts. When Rails developers try out Ecto, they often feel there’s too much boilerplate and believe the Rails design…

Post by elbear » Sun, Jun 22, 2025, 7:34 PM UTC

neuderrek wrote: post #214

freedomben wrote: post #209

Earlier quoted context omitted.

Indeed, why would an employer pay us a high salary to sit by the pool? The benefits will go to the founders/investors and the customers. They'll benefit greatly from the increased output and lower costs, but the middlemen (SWEs) will be cut out. That's a great thing if you're a founder/investor or a customer, but not if you're the middleman. New opportunities may come around, but I don't think that's inevitable. It r…

It will not be easier for founders/investor either. If couple prompts is all it takes to build your product, your potential customers will write those prompts themselves instead of buying your product.

Post by liampulles » Mon, Jun 23, 2025, 9:20 AM UTC

loloquwowndueo wrote: post #241

liampulles wrote: post #228

This is very cool! I will say though, my spidey senses kick in when looking at stuff like this, and make me wonder about how much I'm going to get vendored in here. Could I use it develop a site off fly.io? If the answer is no, then I'd say this is cool and I think useful for people who need something quick and simple and out of the box, but not something I would ever use on a serious production project.

The answer is yes. What would you say then? There’s a “clone Git repo” thing in the left side bar, use that to clone the project locally, mix deps.get, mix phx.serve and you’re up. You can deploy this anywhere you want.

Post by ewuhic » Mon, Jun 23, 2025, 12:18 PM UTC

tyre wrote: post #212

joevandyk wrote: post #115

Earlier quoted context omitted.

The Phoenix.new environment includes a headless Chrome browser that our agent knows how to drive. Prompt it to add a front-end feature to your application, and it won’t just sketch the code out and make sure it compiles and lints. It’ll pull the app up itself and poke at the UI, simultaneously looking at the page content, JavaScript state, and server-side logs. Is it possible to get that headless Chrome browser + age…

When Roo Code uses Claude, it does this while developing. It renders in the sidebar and you can watch it navigate around. Incredibly slow, but that’s only a matter of time.