this post was submitted on 30 Jul 2024
158 points (92.0% liked)

Selfhosted

40347 readers
463 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
 

I saw this post today on Reddit and was curious to see if views are similar here as they are there.

  1. What are the best benefits of self-hosting?
  2. What do you wish you would have known as a beginner starting out?
  3. What resources do you know of to help a non-computer-scientist/engineer get started in self-hosting?
you are viewing a single comment's thread
view the rest of the comments
[–] traches@sh.itjust.works 53 points 3 months ago (26 children)
  • you do not need kubernetes
  • you do not need anything to be „high availability”, that just adds a ton of complexity for no benefit. Nobody will die or go broke if your homelab is down for a few days.
  • tailscale is awesome
  • docker-compose is awesome
  • irreplaceable data gets one offsite backup, one local backup, and ideally one normally offline backup (in case you get ransomwared)
  • yubikeys are cool and surprisingly easy to use
  • don’t offer your services to other people until you are sure you can support it, your backups are squared away, and you are happy with how things are set up.
[–] Findmysec@infosec.pub 3 points 3 months ago (2 children)

Not needing Kubernetes is a broad statement. It allows for better management of storage and literally gives you a configurable reverse-proxy configured with YAML if you know what you're doing.

[–] Nomecks@lemmy.ca 9 points 3 months ago (1 children)

Yes, but you don't need Kubernetes from the start.

[–] Findmysec@infosec.pub 2 points 3 months ago (1 children)

Well I guess podman works fine for the first few months. Interestingly I still use build-ah heavily for building my custom images

[–] Nomecks@lemmy.ca 1 points 3 months ago (1 children)

I find a lot of stuff is using docker compose, which works with Podman, but using straight docker is easier, especially if it's nothing web-facing

[–] Findmysec@infosec.pub 2 points 3 months ago

Funnily enough Docker compose has never worked for me on Podman. There always seems to be something that is incompatible (also due to me running on Debian). However, I feel like it should become a standard amongst homelabbers and professionals to use Kubernetes manifests going forward, since it is the most portable.

[–] keyez@lemmy.world 2 points 3 months ago (1 children)

Heavy disagree on the storage statement from what I've used and seen but it works for lots of people so not going to detract. NFS is always a pain but longhorn seems to have advantages

[–] Findmysec@infosec.pub 2 points 3 months ago

NFS is a pain, no question about it. I used to use longhorn but these days since I'm doing a single node k3s I'm just doing hostpath. It's that PVCs make intuitive sense to me, but I guess podman will likely work just fine for such cases other than canary deployments and OOTB service-meshes

load more comments (23 replies)