Selfhosted
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!
view the rest of the comments
The main disadvantage is it will be very hard to debug and fix when something breaks.
You don't need 90% of this stuff for starting some services if you wanted to do it from scratch, just learn how to use docker compose and a reverse proxy and you'll be all set. You can always add more on later.
This has been my experience self-hosting the normal way though lol. Yeah I've learned a bit but it's not really an area of expertise I'm super keen on expanding. Getting my self-hosted server up was a bloody nightmare. Sharing drives, hardware pass-through with proxmox, containers, samba, mounting drives. There's an endless list of services and configurations that I fucked around with until I got it working, never 100% sure which changes were actually necessary. If an issue comes up I have to relearn the 90% I've forgotten and try and remember wtf I did to get it working in the first place.
All of this is the experience of someone who is more computer literate than 90%+ of the population.
Even learning docker-compose is a task in itself because you need to become accustomed to linux text editors and the linux file structure (which btw is still a complete fucking black box to me).
The need for an app like Cosmos is obvious. There are a million ways to fuck up your home server trying to do it yourself and most of the time you're just following tutorials made by other people. Why not just have an app that follows those tutorials for you and guarantees it's done correct and securely?
omg I literally had to check if I had written this. We are almost the same.
Main difference is that I have a working understanding about linux file structure and am comfortable with text files, but I have only on a couple of occasions even attempted anything with docker. it makes me tired to think about.
Other than that I so feel you on changing things, not knowing what actually fixed the problem. And then having to re-learn everything from scratch on another occasion. I also feel there is a limit to how much I want to learn. I have no aspirations to do this for a living or to become extremely proficient. I have spent the past couple of weekends struggling with drives and shares and permissions etc. It should be simple but it's hard and takes such a long time.
On your advice because it sounds like you are in a similar situation I will try it.
FYI I haven't used cosmos. This post was the first I've heard of it, but I'll likely try to migrate to it at some point.
haha good to know. :)
I was not able to complete the set up. :( I am not given up on it yet though.
The problem is that many people learn by themselves, and leave a security vulnerability. This is designed to avoid that