Selfhosted

59973 readers

408 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

[–] ShortN0te@lemmy.ml 4 points 1 year ago* (last edited 1 year ago) (1 children)

The main difference i would say is the development and licensing model. Photo prism is forcing ppl who want to commit to sign a CLA to.give away their rights. Also the community is not really active it is mainly one dev that can change the code license on any given time.

Immich does not have such an agreement and has a huge active contributor community around it. Also Immich is backed by Futo which has its pros and cons.

Imho the biggest pain in self hosting is when a foss product turns evil towards its community and start to practice anti consumer/free selfhosters business practices.

Immich is far less likely to turn evil.

Edit: I think it is the biggest pain cause you have to migrate every device and person to the new service.

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

Good insights, thank you for the perspective. I will look into that more closely before committing.