3 ms·
Different web apps may use differing DB versions, it happens. I'm merely suggesting docker compose is a fairly simple way to handle this without managing global
by bschwindHN 9y ago
Different web apps may use differing DB versions, it happens. I'm merely suggesting docker compose is a fairly simple way to handle this without managing global installations on a dev machine. Keep in mind this is for local development only, I wouldn't use a docker hosted DB in production though you certainly could if you wanted to.
I've tried several different dev environment setups and this approach yields the fewest frustrations and inconsistencies.
Production is a different story but that's not what I'm discussing here.
- ComputerGuru 9y agoI'm not trying to beat a dead horse here, but what kind of app runs on a database version 5 but not version 6 (for example)? I can see an app relying on features not available in older releases, but databases - of all software - have rock-solid backwards compatibility.
- bschwindHN 9y agoI mean yeah, changing DB minor versions probably won't affect anything, perhaps even changing major versions is alright in most cases. To me, the value is in reducing the number of potential issues a developer can have in their environment and making the build and runtime as consistent as possible. And when the solution is so easy to use, I don't see much of a downside to the docker approach. My team switched from Vagrant to docker compose for our development environments and since then we've had much more stability and have wasted much less time tending to them.