Larabox: The Local Dev Stack Manager that I built.

Good for you. If you’re comfortable wiring everything manually or running Docker setups, stick with it. But acting like that’s the only valid way to work is just ignoring reality. Larabox sits in that space. It’s about speed and convenience, not proving who knows more about server setup. Use it or don’t, it genuinely makes no difference because the app is not for you(Power Users), its for people that don't use docker on windows.

Tools like XAMPP, Laragon, and Laravel Herd exist because a large number of developers don’t want to rebuild the same stack over and over for every project. They just want it running and out of the way.

And yeah, Docker isn’t “complex” if you’ve already invested time into it. But for a lot of people, it absolutely is overhead they don’t need for local dev. Same with manually configuring Nginx, PHP, databases, networking every single time.

Fair points on convenience — I’m not against tools that reduce setup time. I think where I’m pushing back is more on the wording and positioning than the idea itself.

Phrases like “pre-bundled native binaries” and “more optimized for Windows” are a bit unclear from a technical standpoint. Most of these components already ship as native Windows builds, so it’s hard to tell what’s actually being improved or optimized beyond packaging them together.

For newer developers or people who just want to get up and running quickly, I can absolutely see the appeal of something like this. My perspective is just that understanding how the stack fits together (Nginx/Apache, PHP, database, etc.) pays off pretty quickly once you move beyond simple setups.

So yeah — different tools for different workflows. If the goal is speed and reducing repetition, I get why something like Larabox exists. I just think the technical claims could be explained a bit more clearly.

Pre-bundled means, that they are included in the executable. Users don't have to place their own runtimes. and When I say "optimized", Im talking about environment-level tuning, not rewriting the binaries themselves.

I would replace optimised with streamlined maybe.. IMO, leans more on the "convenience" grammar than "technically tweaked" as such.

While I'm in the docker pit for development and wouldn't develop PHP natively in windows (been there, done that 20+ years ago).. I can see the appeal of this kind of setup for people.. let's face it, even with a myriad tools for building your own stacks (of which you can easily "template"), people love herd and valet etc.. so there's a market for it.. especially if it's free and can compete with herd's paid-for features.

Even that aside.. if it's been a technical challenge for you and and offers self-achievement, then I'd say that's a win and a bonus if it becomes more widely adopted 👍🏻

Good luck with the venture! 🙂

Yeah, that's a fair take. I'll revisit the wording on the site, "streamlined" probably fits better.

Appreciate the feedback 👍

:D I think you are reading this wrong. I am not adding nginx/redis/postgres into your composer.json