this post was submitted on 20 Jul 2023
404 points (98.1% liked)

Selfhosted

40359 readers
280 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
404
Hey selfhosters, what are you selfhosting? (chatsubo.hiteklolife.net)
submitted 1 year ago by ratz@chatsubo.hiteklolife.net to c/selfhosted@lemmy.world
171 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
[–] sn0opy@lemmy.world 13 points 1 year ago* (last edited 1 year ago) (2 children)
  • The Lounge (IRC Client)
  • Blocky (local DNS server with ad-blocking)
  • Tailscale (VPN mesh between clients and other servers)
  • Cloudflare-Tunnel (to access some local services directly from the internet via my own domain)
  • traefik (reverse proxy + TLS for all my services)
  • Authelia (auth server for services that don’t have their own authentication)
  • borgmatic (borg backup automation for container data. Pushing backups to borgbase.com)
  • paperless-ngx (document management system)
  • Plex (media server)
  • Tautulli (stats and tracking for Plex)
  • mosquitto (MQTT server)
  • zigbee2mqtt (service to manage my Zigbee devices)
  • Homebridge (service to get z2m devices into Homekit)
  • Homeassistant (home automation)
  • Prometheus (collect stats from several services above)
  • telegraf (more stats collection + server metrics collection)
  • Grafana (for some dashboards that I didn’t want to create in HA)
  • miniflux (RSS reader)
  • Linkding (bookmark manager)
  • Atuin (shell history sync server)
  • uptime-kuma (monitor some external servers + my local internet connection by pinging healthchecks.io)
  • redis (for paperless and some own projects)
  • postgres (for miniflux, atuin and some own projects)

Everything is running in containers on an Unraid server

  • 24 TB usable (16 TB parity drive)
  • 1 TB nvme Cache Drive
  • Intel i3-12100T

With disks at idle/spun down, it consumes roughly 25W.

[–] troy@programming.dev 4 points 1 year ago (1 children)

I have a very similar setup minus the iot and metric related services. I'm managing the services with Docker Compose on unRAID.

[–] jjakc@lemthony.com 2 points 1 year ago (2 children)

What's the reasoning behind using docker compose on unraid, instead of the built in docker implementation?

[–] troy@programming.dev 3 points 1 year ago

For a couple reasons

  1. 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.

  2. 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.

[–] charles@lemmy.ca 2 points 1 year ago

Personally I use it for a couple services that would be difficult to run separately (ie: deemix + lidarr). I'm also planning on moving all of my services with databases over to compose. I do lose a couple other QOL features but I still prefer this approach to start/stop all related containers instead of manually having to close each one.

[–] Cookie1990@lemmy.world 1 points 1 year ago (1 children)

Can you elaborate on your host?

[–] sn0opy@lemmy.world 1 points 1 year ago

What exactly?