Selfhosted

39435 readers

8 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 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

406

Hey selfhosters, what are you selfhosting? (chatsubo.hiteklolife.net)

submitted 1 year ago by [email protected] to c/[email protected]

173 comments fedilink hide all child comments

Nextcloud + OnlyOffice
*arr media management series (Lidarr, Sonarr, etc)
Gitea
Vaultwarden
PiHole
Jellyfin
Wiki-js
Lemmy
Prometheus/Grafana/Loki

Currently all containerised running on a debian VM on a Rockylinux Qemu/KVM hypervisor. Initially I was using rocky+podman but inevitably hit something I wanted to run that just straight up needed docker and was too much effort to try and get working. 🤷

Hardware is an circa 2012 gaming machine with a few ZFS raids for all of my Linux ISOs. It lives an extremely tortured existence and longs for the sweet release of death.

Toying with the idea of migrating it all to on-prem virtualised kubernetes cluster using helm charts to manage the stacks and using NFS mounts for persistent storage because I hate myself (and to upskill I guess)

What about you?

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

[–] troy 3 points 1 year ago

For a couple reasons

Store and version configs in git. I realize unRAID provides flash drive backup (using git also), but this allows me to spin up my setup on another machine that may not be running unRAID. Helped recently when I switched away from Proxmox.
Allows me to group services with their dependencies. ( e.g. postgres, redis, etc ) Also can help isolate service groups from each other. Avoiding port conflicts on common db ports for example. Downside being may have more than one database, redis, etc.

Note, there is an unRAID docker compose plugin so you can still get easy access management buttons to start, stop, view logs, and edit services.