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
Those who run immich, how have you been backing up your library?
My deployment isn't anything fancy, it is currently a Raspberry Pi 4 with a 2TB external drive for the photo library. Been running for more than 6 months with minimal issues. Now that we are at a stable release I need to get some kinda backup going for the photos themselves.
Immich photos are one of the main thing I backup. I use duplicacy and I backup to backblaze B2 storage. It does incremental backups. Same thing with docker persistent data or other things I consider important.
The same way as all other services: all relevant data (compose.yml and all volume mounts) are in a btrfs subvolume. Every night a snapshot gets made and mirrored to a remote server by btrbk.
how much do you pay for the remote server? was thinking about doing something like this for nextcloud (and i might end up using immich in the future)
That server is also a homeserver I manage for family (in another city). The two homeservers then mutually back up each other.
I backup the underlying storage (which is a VM) that immich writes to.
In theory it should be a perfect copy that just crashed.
I run Immich in a VM on Proxmox which gets backed up every 12 hours and all my photos are on the NAS which gets snapshotted every 12 hours and pushed to an external drive and a Hetzner box.
Translation: "I run immich in a virtual machine, which I can manage from a web browser. The photos themselves are stored on a different device which gets backed up to a remote location twice a day."
So why run immich in a virtual machine instead of in, say, a docker? Wouldn't that be way less overhead? (Or is immich the only thing you're hosting?)
I have a docker VM with a gpu passed through/external access (is this called production?) and another docker VM on another machine with no passthrough/external access. So both VMs are running multiple stacks/services and i just assign based on use case. Storage and memory are cheap imo and it's the most secure way to do it with the skill level i have so it's how i run it. I'm sure there's better ways but 🤷♂️
Nothing fancy. I use Backrest for all my backups, and a few of my plans just include the Immich directory. My NAS is an entirely separate machine so my local backups go there, while everything is simultaneously pushed to a backblaze bucket
ZFS sending to a remotelab.
I have Immich on a proxmox container and use proxmox backup. It has already save me once.
I run it baremetal, the photos / videos are all on a separate location (so are "Externsl Libraries" in Immich) and are backed up...
As far as the Immich application itself, I'm not currently backing up anything as I've been trialing it... but, I'll aim to backup any configurations, but I'm thinking to maybe ignore any database - it can just relearn everything if I need to do a restore.... depends how big that DB is...
I clone the dirs nightly to a separate server + storage. Monthly to an offsite.
Borg backup runs every hour on all my docker folders