I now have roughly 100 tests for all the different ways a plan can fail and then recover. @EffectTS_ makes this so damn easy to do, check it out: This `fail` utility can inject failures into resource providers, but only in the context of the passed in Effect.

Time for Opus 4.5 to go brrrrrr and generate all AWS resources.

Better-T-Stack使ってて見つけた、alchemyが良さそうな感じがするので少し頑張ってみるの巻 https://t.co/lncfEH1mjs

@burio_16 @alchemy_run deserves more attention 💯

You can connect Cursor to a running Cloudflare Container over ssh using Warp & Cloudflare Tunnels. This is super secure and doesn't expose the container publicly. I've made a clean example of everything you need using @alchemy_run IaC - GitHub link in thread

I just need 20 lines of @alchemy_run to configure Cloudflare warp so that my laptop can connect securely to my deployed VMs using Warp. This is not even possible with Cloudflare's Terraform Provider.

Looking forward to LiveStore Office Hours #6 in a few hours! Many exciting updates and demos: 🔥 ▪︎ LiveStore 0.4 preview ▪︎ Alchemy demo by @samgoodwin89 ▪︎ Events API by @victorpererik ▪︎ React API by @i_gassmann ▪︎ New tutorial by @nikolasburk Luma link 👇

Do I see @alchemy_run mentioned?

AWS Lambda finally gets Durable Functions. In @alchemy_run (effect), this is all it will take to transform a Function into a Workflow. No directives. No compiler. Just code.

You know @EffectTS_'s abstractions are close to Ground Truth when they invade the entire codebase with ease and I'm not even mad. @alchemy_run's defineStack takes a Stack config object and I think most of the properties are going to be Layers 😅

Here's a pretty minimal setup that supports prod, staging, pull requests and personal dev environments. You just can't beat scripting. P.s. Effect.tap might just be my favorite Effect feature. defineStack.pipe(Effect.tap) beats Outputs any day.

Here's what I am thinking of for cross-stack and cross-stage references. A common case is to have a "Substrate" stack for each AWS account with VPCs, ECS clusters, etc. Account-owners can vend these as "importable" stacks with `defineStack` and Users can reference any stage.

Finally merged the Inputs/Outputs PR for @alchemy_run (effect). Was a brutally difficult task to get it all working with planning and types. Up next: `defineApp`, cross-app and cross-stage references. Then it'll finally be time to pump out Resources.

First time seriously playing around with @alchemy_run for a project partially hosted on Cloudflare. The rest is on Google Cloud and adding support for GCP VM from Docker images took only a couple of hours

I bought and used all the big Starter Codebases (so you don't have to): ShipFast...SupaStarter...Shipped...ZeroToShipped... You name it. Chances are I've tried it. Nothing against their Creators, but they all seemed to promise the same thing: "Ship your Startup in Days, not

The DX @alchemy_run provides is 🤌 To use @CloudflareDev Sandbox SDK, all you have to do is define the container, and Alchemy automatically provisions Durable Object for it!

All the highest-DX technologies in one Tech Stack: Package Manager → @bunjavascript Frontend → @tan_stack Start Authentication → @better_auth Backend → @convex Blob storage → @Cloudflare R2 Payments → @polar_sh Email → @resend Observability → @Sentry + @BetterStackHQ

✨ DX tip for @stripe + @alchemy_run When working with webhooks & local tunneling, you can use `stripe listen --print-secret` to set it in your app. No .env.local or copy/pasting!

tech stack includes: - @tan_stack start, query, form - @convex on the backend, including the @better_auth component for auth, the Workflow component for the main repo analysis, and the RAG and Agent components for AI search and chat - @CloudflareDev (via @alchemy_run) to deploy

IaC → @alchemy_run