Selfhosted
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!
view the rest of the comments
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@copy
and systemd is smart enough to passcopy
into mysql.I did it slightly different, using
systemctl edit mysql@.service
to define different default files for each instance, then[mysqld@copy]
sections in each of those files. Seems like theport
option 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.