3 ms·
But now instead of the annoyance of installing pg, you have the annoyance of installing docker. and then writing a dockerfile. And then bootstrapping docker. et
by TheRealPomax 4y ago
But now instead of the annoyance of installing pg, you have the annoyance of installing docker. and then writing a dockerfile. And then bootstrapping docker. etc. etc. =)
- nicoburns 4y agoInstalling pg is hardly annoying. `brew install postgres`. Done.
- TheRealPomax 4y agoReplied to the wrong person, but I'll take that bait anyway: "Ahahahaha, no". That only works if you live a blissful "all my hosted pg instances use the exact same version" world, which I've never seen be the case for even moderately sized projects. You're going to need multiple Postgres installs if you're going to need pg_dump/pg_restore, which you probably are. (How you solve that problem, of course, is not a one-size-fits-all, and Docker may be the answer... or it may not)
- nicoburns 4y agoDoesn’t pg_dump/pg_restore work across versions? (So long as the CLI tools are the latest version). I guess version compatibility could be an issue in theory, but I’m yet to hit into a backwards compatibility issue with Postgres.
- TheRealPomax 4y agoI wish. You'd think it'd just be able to check the db to see if there's any schema or procedure incompatibility, but it doesn't. Instead, it goes "Remote uses version X and you're using version Y, sort that out" and then it exits.
- nicoburns 4y agoOh, that's incredibly unhelpful!
- Too 4y agoWho, working with these things regularly, does not have docker installed? There is already an official image available so you don’t need to write dockerfile yourself. Having an instance up and running is literally just a docker run command away.