Live data from Hacker News

Postgres.app

postgresapp.com

61–70 of 158 posts

Re: Postgres.app

#61
post #48

Earlier quoted context omitted.

> because then everything is nicely isolated This is why we use SQLite for all the things. I don't even remember what a database installation process looks like anymore. It's just a nuget dependency and some code for us.

Are you using SQLite in production too? I'm curious about your domain - is it a web application or something else?

We do use it in production. Have been for years.

We use it as part of the back-end of a business workflow automation system. Handles 100-1000 concurrent users without any issues.

Re: Postgres.app

#62

I'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 \ -…

I love using Docker Compose in theory, but I've found it really difficult to do local development with a "Docker only" setup on Mac, due to the performance issues with the filesystem layer (even when using cached volumes, etc). Ruby gemfiles and node_modules are big culprits here, since they involve a lot of filesystem accesses to load/install dependencies. It might be more manageable if I was just using Postgres fro…

You could look into Nix for Ruby and Nodejs. I'm not a particularly experienced Ruby developer, but having Nix take care of all versioning and dependencies for me made the whole ecosystem really accessible (in the sense that I don't need to care about most of it). Everything is still in your filesystem so there shouldn't be any performance issues, and you still get the isolation benefits from Docker (like versions and dependencies not leaking from one project to another).

Re: Postgres.app

#63

I'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 \ -…

Docker on Mac is a performance and battery hog in my experience.

It's so bad I just install a RHEL VM and use podman instead. The difference is insane.

Re: Postgres.app

#64
post #42
post #32

Earlier quoted context omitted.

It also keeps yammering on and on about new versions and required updates. Just that is reason enough to get rid of it.

"Oh no, I have to update my software!" Are you serious?

Docker is notorious for completely breaking everything with their updates. They are also very intrusive about it, and make ignoring updates a paid feature.

This isn't just a "i don't want to update" issue. It's a "docker is terrible software and their business model is just as terrible".

Re: Postgres.app

#65
post #35

For a really nice client for macOS see Postico: https://eggerapps.at/postico/ (not affiliated, just a fan)

I would recommend TablePlus as it supports more than just postgres, and is also on Windows if you need it.

Not affiliated, just an extremely happy customer.

Re: Postgres.app

#66

Earlier quoted context omitted.

Docker on Mac is a performance and battery hog in my experience.

It's so bad I just install a RHEL VM and use podman instead. The difference is insane.

In my experience, docker-machine-nfs has the best performance on mac. No syncing of files.

Re: Postgres.app

#67
post #42
post #32

Earlier quoted context omitted.

It also keeps yammering on and on about new versions and required updates. Just that is reason enough to get rid of it.

"Oh no, I have to update my software!" Are you serious?

When they tell you that you need to upgrade if you want fewer updates, you know the daily updates aren't necessary.

Re: Postgres.app

#68

I'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 \ -…

I went down this road for a long time and eventually realised I was gaining very little from it and picking up a bunch of downsides.

Obviously everyone’s experience is different because we’re all doing different things but I mostly work with Rust and Node, I use Postgres.app as a local dev database and just run the code natively, sometimes Node via nvm when I care about specific runtime versions.

It works great. It performs better then any Docker-based solution (I’m on a Mac) and doesn’t leave me with a bunch of weird dangling images/containers/whatever taking up resources. I still like the idea of using the same Docker environment in dev that I use in production but in reality I just don’t need it.

Re: Postgres.app

#69
post #35

For a really nice client for macOS see Postico: https://eggerapps.at/postico/ (not affiliated, just a fan)

I would recommend TablePlus as it supports more than just postgres, and is also on Windows if you need it. Not affiliated, just an extremely happy customer.

Wow, that looks very nice.
Post reply on HN