3 ms·
Yes, maybe it doesn't apply to Java but I've been unable to setup projects on a new machine because library versions changed, external programs became hard to b
by pmontra 9y ago
Yes, maybe it doesn't apply to Java but I've been unable to setup projects on a new machine because library versions changed, external programs became hard to build themselves, some sw is impossible to find anymore (I remember a customer with a prehistoric MySQL, we had to find the oldest available bug compatible version and hope - they had no tests), etc.
A Vagrantfile or a Dockerfile are not enough. You need the actual images.
- rtpg 9y agoOr in your docker file you specify versions of things to install, check in repos to use, etc etc. It's versions all the way down
- ris 9y agoYou're assuming that all those repos are still around 5 years later.
- rtpg 9y agoDefinitely true. Not sure I am a fan of having every git repo having a copy of everything over and over and over, for "ecological" reasons... But it's probably the best way to endure that your builds will work.
- manyxcxi 9y agoThey are if you mirror the Docker registry. We use Sonatype Nexus and get the added benefit of having our own private Docker, NPM, Maven, etc. repositories on top of automatically caching dependencies we use. So now we don’t have to worry about them disappearing AND we don’t have to leave the network to get them... assuming we don’t screw up our server.
- pmontra 9y agoWe own our registry. That's why we have the images for one project. We install from there. What we don't do yet is storing a pristine a VirtualBox image for another project. We should start doing that because sometimes building those images requires a surprising amount of work. Bitrot, etc.