Can't recommend this highly enough. It comes with the full PostGIS stack included, so command-line gdal, ogr2ogr, proj etc. - just add to your path and it's there for you. It runs multiple versions of Postgres, which came to my aid when Homebrew botched an upgrade: I could just copy the data files across to Postgres.app and recover them there. Overall it's so much better than installing Postgres via Homebrew.
Postgres.app
11–20 of 158 posts
Re: Postgres.app
#12I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc.
This is what I've been using for Postgres:
docker volume create postgres
docker run -d \
-p 127.0.0.1:5432:5432 \
-v postgres:/var/lib/postgresql/data \
--name postgres \
--restart always \
postgres
Re: Postgres.app
#13It looks nice for beginners but personally I find that a simple docker-compose file per project that spins up a postgresql container works pretty nicely and is really easy to use. I just run `docker-compose up -d` and I have a database running. Docker containers also stay out of the way of the os and I can run the right versions for whichever project.
> beginners
Why is this for beginners? Because it is so easy to use? I guess I am a beginner then.
> works pretty nicely
Postgres.app works perfectly and is very minimal in system requirements vs having docker running and the amount of storage it requires.
Re: Postgres.app
#14It looks nice for beginners but personally I find that a simple docker-compose file per project that spins up a postgresql container works pretty nicely and is really easy to use. I just run `docker-compose up -d` and I have a database running. Docker containers also stay out of the way of the os and I can run the right versions for whichever project.
> beginners Why is this for beginners? Because it is so easy to use? I guess I am a beginner then. > works pretty nicely Postgres.app works perfectly and is very minimal in system requirements vs having docker running and the amount of storage it requires.
How good is the upgrade story? That's typically the achilles heel of GUI installers (vs. installing using homebrew).
Re: Postgres.app
#15For something similar that also supports MySQL and Redis, DBngin (https://dbngin.com/) is pretty great, from the team that built TablePlus.
Re: Postgres.app
#16Earlier quoted context omitted.
> beginners Why is this for beginners? Because it is so easy to use? I guess I am a beginner then. > works pretty nicely Postgres.app works perfectly and is very minimal in system requirements vs having docker running and the amount of storage it requires.
How good is the upgrade story? That's typically the achilles heel of GUI installers (vs. installing using homebrew).
In my limited experience (no longer using macOS after ~6 years on the platform), homebrew upgrades was broken more often than upgrades provided by GUI applications. I specifically remember a particular postgres upgrade via homebrew went wrong and I had to basically erase all traces of postgres before re-installing again in order to get it to work. On the other hand, I can remember zero times a GUI upgrade went wrong.
Re: Postgres.app
#17I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc. This is what I've been using for Postgres: docker volume create postgres docker run -d \ -p 127.0.0.1:5432:5432 \ -v postgres:/var/lib/postgresql/data \ --name postgres \ -…
Postgres.app supports multiple versions, and doesn't put random files in /etc/foo - everything is in the right place for a Mac app, i.e. Postgres itself is in /Applications and the database is in ~/Library/Application\ Support/Postgres.
Re: Postgres.app
#18It looks nice for beginners but personally I find that a simple docker-compose file per project that spins up a postgresql container works pretty nicely and is really easy to use. I just run `docker-compose up -d` and I have a database running. Docker containers also stay out of the way of the os and I can run the right versions for whichever project.
I do this too, much easier
Re: Postgres.app
#19Use it and love it. I use docker too for ephemeral databases but keep the long-lived ones here. I just wish there was a version of this for mySQL/MariaDB.
DBngin (https://dbngin.com) may be what you're looking for.
Re: Postgres.app
#20I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc. This is what I've been using for Postgres: docker volume create postgres docker run -d \ -p 127.0.0.1:5432:5432 \ -v postgres:/var/lib/postgresql/data \ --name postgres \ -…
Postgres.app supports multiple versions, and doesn't put random files in /etc/foo - everything is in the right place for a Mac app, i.e. Postgres itself is in /Applications and the database is in ~/Library/Application\ Support/Postgres.
That's interesting, but my situation is that I'm developing on macOS and deploying on a linux box so my postgres setup with docker can look virtually identical.