5 ms·
typically I find CMake would do this, or Make, to verify dependencies. Coupled with a packaging system, like debian gives you, this is all pretty straightforwa
by calvinmorrison 4y ago
typically I find CMake would do this, or Make, to verify dependencies.
Coupled with a packaging system, like debian gives you, this is all pretty straightforward.
I ran into this yesterday, and turns out I don't want to install docker just to build a program...
- TheRealPomax 4y agoRight, but there are as many setups as there are potential users, so even if Debian works, that doesn't mean other linux flavours will work as easily, or flavours of BSDs, and then also Macs, and even WSL, or even just plain old Windows. Having an "everyone gets the same thing, so no one wastes time on bootstrapping" solution is a perfect use-case for Docker. And then once the bugs have been found and fixed, and the code is production-ready, you can focus on documenting and scripting the setup procedures for the various operating systems.
- andirk 4y agoAs an aside, may I ask what people's opinion of running docker containers in prod is? The joke "But it works on my local--" "Then ship your local".
- francislavoie 4y agoThe big win of Docker for me is parity between dev and prod. I absolutely run on Docker in prod. It is not just a dev tool.
- tracker1 4y agoBeen using docker in prod for over 5 years now...
- badcppdev 4y agoI don't understand. I thought you needed different docker files for different architecture? x64 vs M1 chips?
- gocartStatue 4y agoOr Nix :)
- TheRealPomax 4y agoExcept of course in this case that's not what you'd be doing. You'd be installing Docker to help beta-test a program, not "just build a program". If you want to help an open source project succeed, having to install Docker is kind of a trivial cost. If you want to use this... probably not a good idea, it's extremely not ready for general use =)