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 have a single ASUS Chromebox M075U I3-4010U which I use as a Docker host. It's neatly and inconspicously tucked away under my TV, and it's quiet even when the fan's on full if a heavy workload is running.
Main Specs:
Full Specs: https://www.newegg.ca/asus-chromebox-m075u-nettop-computer/p/N82E16883220591R
I started off with a single-node Kubernetes cluster (k3s) a few years ago for learning purposes, and ran with it for quite a long time, but have since gone back to Docker Compose for a few reasons:
For logs, I'm only concerned with container logs, so I use Dozzle for a quick view of what's going on. I'm not concerned with keeping historical logs, I only care about real-time logs, since if there's an ongoing issue I can troubleshoot it then and there and that's all I need. This also means I dont need to store anything in terms of logs, or run a heavier log ingestion stack such as ELK, Graylog, or anything like that. Dozzle is nice and light and gives me everything I need.
When it comes to container updates, I just do it whenever I feel like, manually. It's generally frowned upon to reference the
latesttag for a container image to get the latest updates automatically for risk of random breaking changes. And I personally feel this holds true for other methods such as Watchtower for automated container updates. I like to keep my containers running a specific version of an image until I feel it's time to see what's new and try an update. I can then safely backup the persistent data, see if all goes well, and if not, do a quick rollback with minimal effort.I used to think monitoring tools were cool, fun, neat to show off (fancy graphs, right?), but I've since let go of that idea. I don't have any monitoring setup besides Dozzle for logs (and now it shows you some extra info such as memory and CPU usage, which is nice). In the past I've had Grafana, Prometheus, and some other tooling for monitoring but I never ended up looking at any of it once it was up and "done" (this stuff is never really "done", you know?). So I just felt it was all a waste of resources that could be better spent actually serving a better purpose. At the end of the day, if I'm using my services and not having any trouble with anything, then it's fine, I don't care about seeing some fancy graphs or metrics showing me what's going on behind the curtain, because my needs are being served, which is the point right?
I do use Gotify for notifications, if you want to count that as monitoring, but that's pretty much it.
I'm pretty proud of the fact that I've got such a cheap, low-powered little server compared to what most people who selfhost likely have to work with, and that I'm able to run so many services on it without any performance issues that I myself can notice. Everything just works, and works very well. I can probably even add a bunch more services before I start seeing performance issues.
At the moment I run about 50 containers across my stacks, supporting:
If you know what you're doing and have enough knowledge in a variety of areas, you can make a lot of use of even the most basic/barebones hardware and squeeze a lot out of it. Keeping things simple, tidy, and making effective use of DNS, caching, etc, can go a long way. Experience in Full Stack Development, Infrastructure, and DevOps practices over the years really helped me in terms of knowing how to squeeze every last bit of performance out of this thing lol. I've definitely taken my multi-layer caching strategies to the next level, which is working really well. I want to do a write-up on it someday.
Nice write up. Love the pivot to adjust priorities of what , where and how you spend your time