this post was submitted on 19 Oct 2025
119 points (96.9% liked)
Selfhosted
60048 readers
757 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Interesting using systemd for that, I'd probably have chosen containers for that.
What's the reason for replication vs. dumps? Does the client failover to the replica?
I'm not a systemd guru, but it turned out pretty easy. https://dev.mysql.com/doc/refman/5.7/en/using-systemd.html#systemd-multiple-mysql-instances Basically just make
[mysqld@copy]sections in my.cnf thensystemd start mysqld@copyand systemd is smart enough to passcopyinto mysql.I did it slightly different, using
systemctl edit mysql@.serviceto define different default files for each instance, then[mysqld@copy]sections in each of those files. Seems like theportoption for each has to go in a[mysqld]section, but otherwise ok.Replication because I want to put some live data, read-only, on the VPS, exposed to the world while the 'real' database stays safely hidden in my intranet. SSH tunnel so the replica can talk to the real database.