220
The Verge Takes on Self-Hosting for the Masses
(www.theverge.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Oct 2023
220 points (95.8% liked)
Selfhosted
40415 readers
233 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
Projects like Runtipi have potential for the masses, imo. Single click deployment of apps on your own server....if you can get Runtipi installed first, of course. But hey, a step closer I suppose.
I'm very new to selfhosting, only started in earnest in April of this year. So I definitely felt the hosts frustrations in deploying (or trying to deploy) solutions I wanted to take back from Google and Microsoft. I'm still learning and am almost to the point where I'm comfortable pulling the plug on Google photos entirely. But it's a lot of research for newbs.
The problem with those projects like Runtipi is the same you've with Docker - you'll be hostage to yet another platform that can fuck you up at any moment without notice... like Docker hub did.
Docker does not lock you in with the docker hub though. So no hostage taking.
While that isn't false, defaults carry immense weight. Also, very few have the means to host at scale like Docker Hub; if the goal is to not just repeat the same mistake later, each project would have to host their own, or perhaps band together into smaller groups. And unfortunately, being a good programmer does not make you good at devops or sysadmin work, so now we need to involve more people with those skillsets.
To be clear, I'm totally in favor of this kind of fragmentation. I'm just also realistic about what it means.
Linuxserver.io images don't come directly from Docker Hub any more, and I don't know if anyone noticed or cared. They use their own domain lscr.io that redirects to the Docker repository they're using (currently Github) which makes it easy for them to move the repository without breaking things for users. https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter
That approach is a good idea in general. If you're running a medium to large size project, never directly rely on domain names you don't control because it makes it painful to migrate to something else in the future. Even if your own domain just has a bunch of redirects (both URL redirects and email forwarding), it's better than nothing.