Selfhosted

46685 readers

396 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

[email protected]

Prioritizing de-clouding efforts (slrpnk.net)

submitted 3 months ago by [email protected] to c/[email protected]

53 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

(page 2) 3 comments

sorted by: hot top controversial new old

[–] [email protected] 27 points 3 months ago

I'd recommend migrating one service at a time (install, migrate, shake down; next service).

Either prioritize what you want declouded the most, or start with the smallest migration and snowball bigger.

[–] [email protected] 2 points 3 months ago (1 children)

Can’t go wrong with Proxmox. Though, I would recommend thinking about how you want to integrate Storage here. For most of the VMs you’re planning on running now that’s probably not a huge issue currently, but in the long run you’ll want to also replace Google Drive, Photos and Netflix And then you wish you’d thought about storage earlier.

Consider whether you want to deploy a separate NAS box (I can recommend TrueNAS) and do network storage in these cases (and how exactly that’s going to look like), or if you want to put it all on your Proxmox system and maybe run TrueNAS as a VM.

load more comments (1 replies)

[–] [email protected] 9 points 3 months ago (13 children)

Authelia

Think about implementing this pretty early, if your plan is to use it for your own services ( which I'd assume).

load more comments (13 replies)

load more comments