this post was submitted on 08 Aug 2023
23 points (100.0% liked)

Selfhosted

40266 readers
1157 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
23
Is it possible to have just one DB across all services (lemmy.zip)
submitted 1 year ago by dampfnudel@lemmy.zip to c/selfhosted@lemmy.world
14 comments fedilink hide all child comments
 

I'm pretty new to the self hosting thing but I'm enjoying it a lot and want to go a bit further down the proverbial rabbit hole.

I'm looking at a bunch of services and they all require a DB, usually a MySQL DB. It seems counterintutitive to have 20 MySQL databases each in its own Docker container. So is there a way to have one DB across most of my services? (I realize that Nextcloud and other bigger items should have a dedicted DB.)

How would I set up a shared DB in a docker-compose file?

you are viewing a single comment's thread
view the rest of the comments
[–] thomas@lemmy.zell-mbc.com 21 points 1 year ago* (last edited 1 year ago) (1 children)

You would expose the port to your host which makes the db acessible by anything running on the host, docker or native. Something like

`port

  • 5432:5432 `

But I would recommend running a dedicated db for each service. At least that's what I do.

  • Simpler setup and therefore less error-prone
  • More secure because the db's don't need to be exposed
  • Easier to manage because I can independently upgrade, backup, move

Isn't the point about containers that you keep things which depend on each other together, eliminating dependencies? A single db would be a unecessary dependency in my view. What if one service requires a new version of MySQL, and another one does not yet support the new version?

I also run all my databases via a bind mount

`volume

  • ./data:/etc/postgres/data...`

and each service in it's own directory. E.g. /opt/docker/nextcloud

That way I have everything which makes up a service contained in one folder. Easy to backup/restore, easy to move, and not the least, clean.

[–] Ricaz@lemmy.world 6 points 1 year ago

I would just have Postgres running statically on some solid hardware. It's easy to configure permissions and connections, too.

Not too hard to set up streaming replication for a hot standby if you wanna be sure (or offload some reads).

I use Postgres btw