Live data from Hacker News

Show HN: Devbox – Containers for better dev environments

devbox.ar0.eu

51–60 of 65 posts

Re: Show HN: Devbox – Containers for better dev environments

#51
post #16

Earlier quoted context omitted.

Yes, it feels very similar to Devcontainers. But having tried Devcontainers a lot, it feels like its probably a complex specification since outside of VSCode every implementation has issues. The CLI on Mac has weird user permission issues. Cursor's implementation is very flaky. Zed doesn't implement it yet. So maybe there's space for more solutions in the same space but Devcontainers are very feature rich. And not to…

This has been my experience. I don't use VSCode and every time I've attempted to play with devcontainers I've just given up and gone back to a docker compose file. I love that they tried to extract the feature out into a stand alone thing, but the juice doesn't seem to be worth the squeeze yet.

Devcontainers work nicely with docker compose. It's the only way I use it... Really nice to have it all run containers.

https://code.visualstudio.com/docs/devcontainers/create-dev-...

Re: Show HN: Devbox – Containers for better dev environments

#53
I am afraid that despite all these options for containers, I still use my Vagrant scripts that build whole VMs based on my own schemes, use an apt package cache on the host and manage .ssh/config for me to make VSC remotes more seamless.

Almost all my stuff still runs on simple VMs because I cannot rely on my clients to take on more complex cloud infrastructure and I don't want to be stuck managing all of the things forever, so my life involves building customer VMs from build scripts that are adequately similar to my Vagrant boxes.

I use the VMs a lot for simple tests (e.g. of wordpress plugins and themes) so I have gone to the trouble of setting up Avahi with alias support, adding options for mailhog, different databases, different webserver setups I use for WP or Laravel or node.js, setting up an automated WP install etc.; so there are two or three starting configurations. I even had one for Magento before I realised I could be a lot happier without Magento in my life.

I guess it looks a fair bit like devcontainers now, and I should consider migrating over to that. But it's solid and under my control and that counts for a lot.

Re: Show HN: Devbox – Containers for better dev environments

#54
post #7

Earlier quoted context omitted.

I am not affiliated with Microsoft and I anal but I think dev box is fine. What we want to avoid is the term dev containers. https://containers.dev/

The overlap with Jetpack's devbox name is not fine. Not morally, given the massive overlap in functionality between the two implementations. At the very least, their existence will prevent you from getting a trademark. Both projects even use devbox.json for their definitions, for crying out loud. If your usage is not compatible with Jetpack's devbox.json, please switch to a different filename ASAP.

I didn't realize our similarities until after i designed like all of it, i didnt do any research before hand sadly causing a lot of issues like this

Re: Show HN: Devbox – Containers for better dev environments

#55

Looks like a really fun project. You might want to reconsider the name though, since there is this other devbox from Jetify https://www.jetify.com/devbox that also received quite some attention on HN a while ago https://news.ycombinator.com/item?id=32600821

Good point. I remember testing out Jetify's version a while back and switching away from it due to some issue I was having. I 100% thought this project was the same, just with a new website, as I did not remember much of the implementation details. Both of them even use `devbox.json` as the configuration file...

Well its not the same programming wise so your problem might be fixed on ours but as i said in another reply i wasnt aware of the existing project and our overlaps i did no research before hand sadly

Re: Show HN: Devbox – Containers for better dev environments

#56
post #10
post #5

FYI there's a well-starred, corporate-backed, similar functionality, Nix-based product with the same name: https://github.com/jetify-com/devbox https://www.jetify.com/devbox

I thought that OP linked this devbox since so many subcommands from the cli are almost identical

Again another oversight i also didnt relise i was mirroring docker commands and npm.

Re: Show HN: Devbox – Containers for better dev environments

#57
post #37

I had a very strong personal opinion that, unless you expect frequent migrations or horizontal scaling, Docker is overkill and could be considered as bloat in many instances. After I joined my new company, I found out about devbox, and I love it. Now I use it for almost every personal project. It helps you to make the environment reproducible without sacrificing performance. However, I use https://www.jetify.com/devb…

Yeah... i didn't realize this was a project before hand, do they use their own container framework? seems like too much for my small project but i can apricate your input.

Re: Show HN: Devbox – Containers for better dev environments

#58
post #28

I've been using Docker containers for quite some time to do web dev work. The one thing I haven't yet set up is doing mobile dev in a docker environment. Does devbox support mobile development - Flutter or ReactNative?

Yes hypothetically i haven't tested it but i am not sure why it wouldnt aside from machine constraints
Post reply on HN