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
I wanna get into it but man, the mountain of knowledge I need to even understand what people are talking about is hard to climb. I'm trying to just get some stuff running in docker and it fails to launch and I'm like... How?! Isn't that the whole point of docker lol. Baby steps I guess
It's messy. Dockers superpower: You can write a crazy ass python application that needs dozens of dependencies and weird software configured. You put it into a container, you can update and publish the container with a single script call. Other people can install that, set some variables and not have to install the dozens of other pieces of software. They also don't have to worry about updates.
But that's not to say you don't have to worry about networks, storage and ports.
Then the simplicity of the configuration of containers depends upon the person that made the container. Maybe they wanted to be very flexible and there are dozens of things you need to set. Maybe they didn't include the data store internally in that container and you need your own data store in another container.
I felt exactly the same when i started - the learning curve is real! Try TrueCharts.org or linuxserver.io for reliable docker templates with good docs that actually work, saved me so much troubleshooting headache.
Thanks will do!
I've learnt it from scratch in my week off, spending 2 or 3 hours on it every night for a week (although this might be underselling it as I had become familiar with desktop Linux over the past year and had a superficial idea of Docker containers with my Synology NAS). But still it's not as big a deal as you think once you find some good resources. I'm going to comment about my setup after this in this thread.... Have a look.
Main resource that helped me was Marius Hosting and ChatGPT got me out of trouble when I got stuck by deciphering logs for me when things didn't work.
Thanks. Yeah I'm just trying to work at it slowly in my downtime instead of just watching YouTube all night.
Check out Cosmos, I struggled piecing things together but when I restarted from scratch with this as the base is has been SO much easier to get services working, while still being able to see how things work under the hood.
It's basically a docker manager with integrated reverse proxy and OpenID SSO capability, with optional VPN and storage management
Im at the level where I don't know what SSO means. I can follow instructions to change a DNS. But what a DNS actually is I don't know. Which is fine, until I need to work out what's broken
SSO is "single sign on". DNS is "domain name service", which is just a way to turn a hostname (like www.google.com) into an IP address. It's sort of like a phone directory, but for the Internet.
SSO is single sign on, so you don't need individual username and password for every service. It's a bit more advanced so don't worry about it until you have what you want working properly for a while.
DNS is like the yellow pages of the internet - when you type www.google.com your computer uses a DNS server to look up what actual IP address corresponds to the website name. The point of Adguard or pihole is that when a website tries to load an ad your custom DNS server just says it doesn't recognize the address
Oh like a custom yellowpages, sick!
Sometimes you just need to start small and not worry about over complicating things. I started my journey in 2011 running Plex on a crappy laptop
Are you doing things through docker compose? If so, feel free to PM me or reply here with your compose file and I'll help as best I can
Docker should be trivial to run. Hopefully it gives you some useful messages in the logs.