Selfhosted

59854 readers

686 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How do you manage you DB in a docker environment? (sh.itjust.works)

submitted 10 hours ago by Croquette@sh.itjust.works to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

Hello,

As the title suggests, how do you manage your DBs for docker services.

Do you spin a new DB for every new docker cluster or do you have a centralized DB that is accessible to the docker clusters.

What are the pros and cons of both method?

For the moment, I spin a new DB for every services as I feel it is easier to backup the service in case of a problem.

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

[–] Croquette@sh.itjust.works 1 points 7 hours ago

That's a good perspective.

Also I hate docker in general. I understand why people use it. It's the same reason I use it.

I am the same. But many services offer docker as the main installation method and many times, the bare metal method is poorly documented.

So docker it is. And it's a good skill to have no matter what since it is so widespread.

I never thought about the issues of setting a docker service with an external database. I don't mind dealing with the users and tables of a database, but having to dig deep in docker compose settings is always a bad time.