Selfhosted

41723 readers

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

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Prioritizing de-clouding efforts (slrpnk.net)

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

40 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

[–] thejevans@lemmy.ml 7 points 20 hours ago (4 children)

I would recommend running Home Assistant OS in a VM instead of using the docker container.

[–] mcchots@sh.itjust.works 2 points 19 hours ago (2 children)

Why is that?

[–] thejevans@lemmy.ml 4 points 18 hours ago

Everything @CondorWonder@lemmy.ca said and because backups to Home Assistant OS also include addons, which is just very convenient.

My Proxmox setup has 3 VMs:

Home Assistant OS with all the add-ons (containers) specific to Home Assistant
TrueNAS with an HBA card using PCIe passthrough
VM for all other services

Also, if you ever plan to switch from a virtualized environment to bare metal servers, this layout makes switching over dead easy.

[–] CondorWonder@lemmy.ca 4 points 19 hours ago

You get easy access to their addons with a VM (aka HAOS). You can do the same thing yourself but you have to do it all (creating the containers, configuring them, figuring out how to connect them to HA/your network/etc., updating them as needed) - whereas with HAOS it generally just works. If you want that control great but go in with that understanding.

load more comments (1 replies)