Are you reusing one postgres instance for all services? (jemmy.jeena.net)

submitted 7 months ago* (last edited 7 months ago) by jeena@jemmy.jeena.net to c/selfhosted@lemmy.world

42 comments fedilink hide all child comments

I have many services running on my server and about half of them use postgres. As long as I installed them manually I would always create a new database and reuse the same postgres instance for each service, which seems to me quite logical. The least amount of overhead, fast boot, etc.

But since I started to use docker, most of the docker-compose files come with their own instance of postgres. Until now I just let them do it and were running a couple of instances of postgres. But it's kind of getting rediciolous how many postgres instances I run on one server.

Do you guys run several dockerized instances of postgres or do you rewrite the docker compose files to give access to your one central postgres instance? And are there usually any problems with that like version incompatibilities, etc.?

you are viewing a single comment's thread
view the rest of the comments

[-] matto@lemm.ee 13 points 7 months ago

Not so long ago I had the same question myself, and I ended up setting 1 Postgress instance and 1 MySQL instance for all services to share. In the long run, I had so many version and settings incompatibilities across services that moved back to one DB per service that is tuned specifically for it. Also, I add a backup app to all my docker compose files that have a DB in it. This way, backups happen periodically and automatically.

[-] richmondez@lemmy.world 6 points 7 months ago

Which db backup app do you use if you don't mind me asking?

[-] tritonium@midwest.social 3 points 7 months ago* (last edited 7 months ago)

You don't need a db backup app... bind mount the data to a location then just stop the container and have borg take the backups. You can do this with all your containers.

/docker/postgres

/docker/postgres/data

/docker/postgres/compose.yml

And do that with every container. Easy as fuck to backup and restore them.

[-] matto@lemm.ee 1 points 6 months ago

Sorry! I know it's been ages, but this is what I use:

For Postgres: https://github.com/prodrigestivill/docker-postgres-backup-local
For MySQL: https://github.com/fradelg/docker-mysql-cron-backup

this post was submitted on 22 Mar 2024

48 points (96.2% liked)

Selfhosted

39677 readers

355 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz