Stacktora - Bootstrap. Once. Everywhere.

@elifeakekep6oh Thanks so much for giving it a spin! That first-run experience is exactly what we obsess over. If a developer can clone, generate, and get running without fighting their environment, we've done our job.

I'm especially glad you called out the Makefile. It's one of those small details that can eliminate a surprising amount of tribal knowledge and onboarding friction across a team. That's ultimately what Stacktora is about—making your stack repeatable, shareable, and consistent from day one.

Really appreciate you taking the time to test it, and if you have any ideas or rough edges you run into, I'd genuinely love to hear them. We're building this alongside the developer community. 🚀

@sunakphh — the generated files are never meant to be hand-maintained individually — stacktora.json is the single source of truth, and every file (compose, Makefile, CI, README, the works) is deterministically regenerated from it. So "staying coherent" isn't something you have to manage yourself, it's the actual mechanism. Change a runtime version or add a service in the recipe, re-run `stacktora sync`, and the whole set updates together instead of drifting apart the way hand-edited configs do.

That's also why the CLI has a `check` command separate from `sync` — it diffs your working files against what the recipe would generate, so you can see drift before it becomes a production surprise, even if someone on the team hand-tweaked a file directly.

The honest tradeoff: if you need something the generator doesn't support yet, you're stuck editing a generated file directly (which then technically "drifts" until the recipe catches up) or waiting on us to add it. We're expanding coverage steadily, but it's worth knowing going in.

Appreciate you actually digging into the mechanics instead of just kicking Stacktora's tires — exactly the kind of question I like getting on launch day.

Ezra