Selfhosted

60048 readers

721 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

119

Selfhosting Sunday! What's up? (lemmy.nocturnal.garden)

submitted 8 months ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world

113 comments fedilink hide all child comments

What's happening on your servers? Any interesting news things you tried?

I didn't do anyone other than updating Mastodon (native deployment) lately due to a lack of time. Reading so much about Immich caused me to consider trying it in parallel to Nextcloud but I'm not sure if I want to have everything twice.

Not quite homelab, but I'm about to install Linux Mint on my mom's laptop and that had me thinking about creating an off-site backup in her place again since she has a fiber connection. I'm still not sure about the potential design though, but currently my only backup is in the same rack as the live stuff.

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

[–] tburkhol@lemmy.world 2 points 8 months ago (2 children)

I've been trying to convince a VPS to run two instances of mariadb - one for local databases, one to replicate the homelab. Got mariadb@server and mariadb@replica sorted out through systemd, but now stuck on replication from mysql to mariadb. Looks like I'll be ripping out mariadb and putting everything on mysql.

[–] RheumatoidArthritis@mander.xyz 2 points 8 months ago (1 children)

Have you checked if statement-based replication works from mysql to mariadb?

[–] tburkhol@lemmy.world 1 points 8 months ago* (last edited 8 months ago) (1 children)

I'm hung up on unrecognized charset #255. Tried rolling everything back to utfmb3; suppose I could go all the way to Latin1. I imagine there's a lot of depth I could learn, but dropping mariadb for mysql seems like the path of least resistance right now.

eta: got the character set sorted. Had to make a new dump, confirm that everything in the dump was utf8mb3, then re-prime the replica with that data. Wasn't enough just to change the character sets internally.

[–] RheumatoidArthritis@mander.xyz 2 points 8 months ago

So it works now! Good job

[–] tofu@lemmy.nocturnal.garden 1 points 8 months ago (1 children)

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?

[–] tburkhol@lemmy.world 3 points 8 months ago

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 then systemd start mysqld@copy and systemd is smart enough to pass copy 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 the port 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.