makes me wander, what ai/prompt did you use to generate the pic. Looks neat!
this post was submitted on 30 Jan 2024
186 points (95.6% liked)
Selfhosted
40165 readers
784 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 1 year ago
MODERATORS
Looks like you wandered into autocorrect changing the word "wonder" on you
Nice chair
I use DALL·E via ChatGPT Plus. The prompt is the first two paragraph in this post plus "Draw a picture for this article titled My 2023 Homelab Setup".
I retried several times and picked my favorite one :)
I really like self hosting too but Kubernetes is overkill in complexity. I use nomad. :)
In a cluster? I'm actually thinking about using Nomad between my three sff pc that I use as servers, but I have no clue as to how to sync storage between them (container side I mean, with nextcloud data for example)?
Storage is hard to do right :(
If you can get away with it, use a separate NAS that exposes NFS to your other machines. Iscsi with a csi might be an option too.
For databases, it's usually better to not put their data on shared storage and instead use the databases built in replication (and take backups!).
But if you want to go down the rabbit hole, check out ceph, glusterfs, moosefs, seaweedfs, juicefs, and garagehq.
Most shared file systems aren't fully posix compliant so things like file locking may not work. This affects databases and sqlite a lot. Glusterfs and moosefs seen to behave the best imo with sqlite db files. Seaweedfs should as well, but I'm still working on testing it.
Yep, as someone who just recently setup a hyperconverged mini proxmox cluster running ceph for a kubernetes cluster atop it, storage is hard to do right. Wasn't until after I migrated my minor services to the new cluster that I realized that ceph's rbd csi can't be used by multiple pods at once, so having replicas of something like Nextcloud means I'll have to use object storage instead of block storage. I mean. I can do that, I just don't want to lol. It also heavily complicates installing apps into Nextcloud.
Yeah in a cluster with consul. Consul gives automatic service discovery and works with traefik so I don't even have to care which node my service is running on since traefik knows how to find it using consul.
For the storage I went with a simple solution. I installed nfs on a machine running in nomad, and then configured the nomad clients to mount that disk. All of this with ansible so I don't have to do it more than once.
Nice setup. Going to steal some ideas for my own setup!
Nice, gave me a couple of ideas about some other software I might be interested in hosting for myself.
I couldn't get the top-level navigation shortcuts to work in your blog, just FYI.
Thanks for pointing out! It should be fixed now 😄
The manifest of my Kubernetes cluster is managed in a Git repository and is automatically deployed via a GitOps tool named Flux CD. When I push changes to the repository, such as adding a new application or upgrading Docker images, the deployment occurs within a few minutes.
This is the way.
Although I use Flux ImageUpdateAutomation instead of Renovate Bot. Did you consider using Flux to do auto updates? Are there any downsides that made you choose Renovate Bot instead?
Thanks! I looked at the documentation of Flux image update automation first but I didn't figured out how to handle Helm chart versions, and it seems it requires manual "marker" to handle image tags in Helm values (which Renovate can manage automatically), so it looks like Renovate fits my needs more.
Is that really the chair you're going for?