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 3 raspberry PIs, 4 various lenovo tiny PCs all in a kubernetes cluster and it seems I need more RAM than CPU. Storage is on a DIY NAS with 8*8TB disks in a raid 6.
I run bookstack, nextcloud, 2007scape, gitea, synapse, the *are stack, Plex, and a bunch of other things.
If I was just starting out I'd grab a used lenovo tiny or two, set up a docker cluster and play with that. There is software to replicate local storage across nodes that I've never touched but I'd try out a few of them also if you don't want to use a NAS. Worst case, just use local storage and the containers will be locked to that host.
I think Proxmox let's you run VMs and Containers too if you prefer that route.
Why swarm and not not k3s?
What are the practical differences between swarms and k3s?
The control plane, I guess…
I've never actually used swarm so I could be wrong. However, I was under the impression that Docker swarm is a lot easier to use with a lot more examples for people to deploy their Containers.
With K8s/K3s I find myself translating a lot of docker examples into deployment yamls with Services, Network Policies, PVCs, secrets, etc, etc. It's just a lot more lines in the .yml files. This also assumes you know that anything that you run in docker you can run in K8s with 1 replica and more is not ideal.
Ok, k8s is harder but I feel that applying configuration remotely is more robust. I haven’t used swarm though.