Selfhosted

60024 readers

736 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

Prioritizing de-clouding efforts (slrpnk.net)

submitted 1 year ago by meyotch@slrpnk.net to c/selfhosted@lemmy.world

52 comments fedilink hide all child comments

I am finally making the push to self host everything I possibly can and leave as many cloud services as I can.

I have years of linux server admin experience so this is not a technical post, more of an attempt to get some crowd wisdom on a complex migration.

I have a plan and have identified services i would like to implement. Take it as given that the hardware I have can handle all this. But it is a lot so it won’t happen at once.

I would appreciate thoughts about the order in which to implement services. Install is only phase one, migration of existing data and shaking everything down to test stability is also time consuming. So any insights, especially on services that might present extra challenges when I start to add my own data, or dependencies I haven’t thought of.

The list order is not significant yet, but I would like to have an incremental plan. Those marked with * are already running and hosting my data locally with no issues.

Thanks in advance.

Base system

Proxmox VE 8.3
- ZFS for a time-machine like backup to a local hdd
- Docker VM with containers
  - Home Assistant *
  - Esphome *
  - Paperless-ngx *
  - Photo Prism
  - Firefly III
  - Jellyfin
  - Gitea
  - Authelia
  - Vaultwarden
  - Radicale
  - Prometheus
  - Grafana

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

[–] just_another_person@lemmy.world 6 points 1 year ago* (last edited 1 year ago) (2 children)

The biggest thing I'm seeing here is the creation of a bottleneck for your network services, and potential for catastrophic failure. Here's where I forsee problems:

Running everything from a single HDD(?) is going to throw your entire home and network into disarray if it fails. Consider at least adding a second drive for RAID1 if you can.
You're going to run into I/O issues with the imbalance of the services you're cramming all together.
You don't mention backups. I'd definitely work that out first. Some of these services can take their own, but what about the bulk data volumes?
You don't mention the specs of the host, but I'd make sure you have swap equal to RAM here if youre not worried about disk space. This will just prevent hard kernel I/O issues or OOMkills if it comes to that.
Move network services first, storage second, n2h last.
Make sure to enable any hardware offloading for network if available to you.

[–] Cerothen@lemmy.ca 3 points 1 year ago

Proxmox backup server is my jam, great first party deduplicated incremental backups. You can also spin up more than 1 and sync between them

[–] meyotch@slrpnk.net 1 points 1 year ago

I have a fine backup strategy and I don't really want to go into it here. I am considering my ecosystem of services at this point.

I am skeptical that this will overload my i/o if I build it slowly and allocate the resources properly. It may be the rate-limiting factor in some very occasional situations, but never a real over-load situation. Most of these services only sit and listen on their respective ports most of the time. Only a few do intense processing and even then only on upload of new files or when streaming.

I really resist throwing a lot of excess power at a single-user system. It goes against my whole ethos of appropriate and proportional tech.