2 ms·
We seem to be talking about different kinds of servers. You say: > at some point the code has to go from dev code to production code. If you're managing dev an
by pdonis 6y ago
We seem to be talking about different kinds of servers. You say:
> at some point the code has to go from dev code to production code. If you're managing dev and production in different ways, then you're going to have to spend significant time "productionising" your dev code
This is true, but as I understand the article we are talking about, it wasn't talking about a dev workstation and a production server for the same project or application. I can see how it could make sense to have those running on the same machine (but probably in containers).
However, the article was talking about a dev workstation and a home server which had nothing to do with developing code, but was for things like the author's personal email and web server. Trying to run those on the same machine was what caused the problems.
- lmm 6y agoI presume what the author is developing is code that they're eventually going to want to run on their home server, at least if they get far enough along with it. What else would the end goal of a personal project be?
- mattmanser 6y agoReading this chain, you seem to want it both ways, that a Dev machine runs unstable config and is in an unknown state due to random package installation, but the same machine should be stable and reproducible.
- lmm 6y agoYes, that's exactly why the OP's approach is appealing! I want it to take minimum effort to install some random new package/config/dependency, but I also want my machine to be stable and reproducible.
- pdonis 6y ago> What else would the end goal of a personal project be? Um, lots and lots of possibilities?