Show HN: I got tired of managing dev environments, so I built ServBay
servbay.comOne small feedback: It took me a while to figure out what it actually does. The homepage makes it look more like coolify or dokku.
So at your core you’re trying to solve an Apple bug?
The "why not use Docker?" question isn't really answered very well. If you're developing on Linux the obvious answer is that something based on containers is going to be a lot more robust and make more sense than this.
I could see this product being used by someone who is trying to untangle some legacy spaghetti, but to me it seems like if you introduced this to a new development workflow you'd be cementing some outdated and dangerous practices - a lot of stuff here happening outside of source control.
If you added a feature to push/fetch and sync the local development database from an s3 (or like bucket) it would solve one of the real core problems of new developers getting started.
That nginx proxy probably works 99.999% of the time, but oh boy, is that .001% going to tick someone off. Proxy's always add a small layer of complexity that can fubar things in strange ways, i know from running many of proxies in production just fine until that tiny little app/proxy config change that borks it. I haven't dug in enough yet, but i hope it can be bypassed.
Ambitious project that I think has some legs. A lot of devs dislike docker and many teams struggle to use it well anyway (for instance, a good dev Dockerfile is usually not the same as a good production Dockerfile). You will need to make this more "IAC-like" if you want to beat it though, imho.
Keep going and good luck!
> The project is still young
But the website is stuffed with AI and yet "Trusted by over 100,000 developers worldwide"?
Doesn't pass the smell test for me.
1. In a team environment, this seems like it would cement bad long-term practices into your workflow. So much is happening outside of source control. I see there's a unified configuration feature but it seems like a GUI of various ways to make a big mess that your future DevOps team is going to facepalm about and untangle.
2.
> For years, my local development setup has been a fragile mess of tools that never quite played nicely together. On my mac, it was a constant battle with Homebrew services starting (or not starting) on boot, conflicting PHP and Node versions managed by `asdf` or `nvm`, and a collection of `docker-compose.yml` files that I'd copy-paste and tweak for every single project. The cognitive load was just too high.
This to me reads as "I don't know what I'm doing and I'm having a bad time." Me personally, I'm not copying and pasting docker-compose.yml files around manually, I'm using source control with a development team and using feature branches like a well-adjusted person. I'm not constantly battling with Homebrew, none of my development environments depend on Homebrew as that is not what the tool is for.
3. In the demo video, the use of AI imagery (of a particularly low quality) and the AI narrator seems very lazy and makes me think that I shouldn't use the app because it might be AI slop with lots of bugs and security issues. I'd rather see a demo given by someone who isn't the best speaker than hear a fake AI voice.
4. The "Why not just use Docker?" question has not been sufficiently countered.
The idea of paying double digits annually for a service that's basically a weaker version of Nix, and which lacks Linux support, is absurd.
3 more comments available on Hacker News