HomeLab VS awesome-selfhosted

And if you are interested how I've done it: https://github.com/Michaelpalacce/HomeLab

Example of a service that is being backed up (see backup.velero.io/backup-volume): https://github.com/Michaelpalacce/HomeLab/blob/master/Helm/apps/uptimekuma/templates/deployment.yaml

But for me https://github.com/Michaelpalacce/HomeLab/tree/master/cluster/homelab/apps

So I've been trying to get botkube to work, but it seems to me like the helm chart documentation is outdated? I've been looking at the values and trying to make things work and it didn't really work for me.. https://github.com/Michaelpalacce/HomeLab/blob/master/cluster/homelab/apps/botkube/helmrelease.yaml is what I tried

And here is some documentation and specifics I've ran into. https://github.com/Michaelpalacce/HomeLab/blob/master/docs/Backups.md

Also for configuration storage and git, I recommend taking a gitops approach to things. You can checkup FluxCD2. Here is my repo for reference https://github.com/Michaelpalacce/HomeLab

A few suggestions and thinks I wish I knew when I started ( personal opinions incoming ): 1. Get a single well sized server ( I'd go for 8 cpus .. And like more than 16 gigs of ram and 250+ ssd, ideally m.2 nvme ). Don't bother with raspberry pis.. Check my profile for my previous post to see a comparison of raspberry pi cluster and a x86 cluster... 2. Install proxmox to do virtualization 3. The majority of People in this sub hate kubernetes and the minority is scared to speak, but install k3s on the vms you spin up, this way you can scale resources and not worry about some elaborate setup of which containers go to which node and how to setup tls offloading, load balancing and much much much more as kubernetes will handle it for you. ( bonus since you are a devops engineer so you are probably used to kube clusters ) 4. Use Velero to do restic backups to s3 for services that are critical like dbs and password managers etc. 5. Do everything with ansible or GitOps! My personal homelab is here: https://github.com/Michaelpalacce/HomeLab utilizing ansible, flux for GitOps and renovate to keep my services up to date ( note to say my cluster spin up isn't as nice as I want it to be since when provisioning I have a Dependency on some secrets which I do manually.. But this is only first cluster setup ) 6. Setup a VPN and administrative services on the raspberry pi you have lying around. Personally my VPN is on the router but if yours doesn't support it, do that. 7. After you are done setting everything up and you have a backup, format the drives and reinstall the vms and re set everything up. Document the process, write automation scripts until satisfied... I genuinely recommend you do this like 3 times...... 8. Vpn I guess a lot of people like wireguard or adguard home... Doesn't really matter as long as it's not open vpn and it supports multiple threads. 9. Setup nodered for some automation around your new home, you'll love it. 10. Firefly is amazing! 11. Make sure that your CSI ( Container storage interface ) supports replication. Keep 3 replicas of critical volumes! 11. If you need any help, don't forget to ask :) personally shoot me a dm and I'll do my best to help, but I'm sure most of us here would

None of these lists ever seem to be as fleshed out, up to date, or well organized as https://github.com/awesome-selfhosted/awesome-selfhosted , though imo any more attention on the self hosted scene is awesome. We're now self hosting everything at my co-op, and it's a dream. Saves us money, provides learning opportunities, potentially is getting us work (managed hosting providers asking if we can be a devshop for their clients, for example), and lets us give back to the FOSS community as we uncover bugs.

We use:

* Matrix / Synapse for comms (slack alternative) (managed hosting through etke.cc)

There are a ton of resources about HW aspects of home labs for beginners but not so much for what to run on them and why. There are lists like https://github.com/awesome-selfhosted/awesome-selfhosted but they are confusing for absolute beginners like me. Are there any good SE project guides you know?

This[1] seems like a well maintained repo.

And thank you for the pointers, we'll try to get ourselves added here :)

[1]: https://github.com/awesome-selfhosted/awesome-selfhosted

I've always felt like FOSS as a philosophy has been tangled up in trying to participate effectively in capitalism, when that was never really the point, nor really very possible unless you're lucky, nor really worth it. The origin of FOSS as I understand it from reading books like "Hackers" is from people that were mad that access was being restricted to systems and code from people that really wanted to use these systems and code, and hack them, and learn from them. I recall that one of the things Stallman likes to brag about from that time is not related to FOSS at all, but instead successfully decrypting a bunch of passwords, emailing the decrypted passwords to people, and recommending they instead set the password to an empty string instead. It was about keeping access to the system Free as in Beer.

I suppose some have argued that FOSS represents a Public Commons in the way that fields and wells and physical markets used to, but none of those things survived capitalism, so I don't see why a technological commons should be expected to either.

For me I've been thinking lately that perhaps those interested in FOSS should instead consider how we can use FOSS to detach ourselves from needing to participate in global capitalism at all. Is there FOSS technology we can use to liberate people from things they need to spend money on right now? An example could be the Global Village Construction Set: https://www.opensourceecology.org/gvcs/ a set of open source designs for things like hydraulic motors or microcombines or steam engines that you can build on your own, usually not for cheap, but for far, far cheaper than you could buy from John Deere. Here's another cool project, some guy has just been building things like solar panels and basic circuit boards on his property from very base components for years: https://simplifier.neocities.org/

Some other FOSS liberation examples:

Combining a tool like Jellyfin with Sonarr, Radarr, and etc, can liberate people from their 5 different media subscriptions. Or at least they can still buy DVDs and put them on Jellyfin to have the convenience of streaming with the media library of their own choosing.

Deploying Matrix or another FOSS communication tool can let organizations have enterprise-level communication software without paying HUGE seat-based license fees to corporations like Slack.

In fact there's many ways to liberate yourself from paid SaaS in this list: https://github.com/awesome-selfhosted/awesome-selfhosted at my co-op we self-host and deploy all our services for this reason, it saves us a TON of money.

I don't have many other examples to mind because this is something I'm actively still researching. Friends in Venezuela though especially tell me how FOSS technology can liberate in ways I wouldn't expect here with my 64gb RAM machine with the latest processor, that I can easily replace components on on a whim. Such as how they can keep all their broken down machines pieced together from junkyards running pretty ok on various linux distros, and how they can sell creative work using free tools like gimp (no, really) or darktable. Like as not they'll just pirate software, though, but apparently FOSS often runs better on shitty hardware.

Anyway my long term plan is to find or build more and more things that let people just not spend money on things anymore. That could be by making it easier to not have to throw things away anymore, or building tools to replace proprietary ones, or, idk, other ways I haven't thought of.

Dashboard in what sense? Is this what you had in mind or no?

https://github.com/awesome-selfhosted/awesome-selfhosted#per...

I often skim through various "awesome lists" (e.g. [1]) and communities interested in open source apps like r/selfhosted [2]

[1] https://github.com/awesome-selfhosted/awesome-selfhosted

[2] https://www.reddit.com/r/selfhosted/

1. https://nextcloud.com/ https://proton.me/drive https://github.com/awesome-selfhosted/awesome-selfhosted#fil...

2. Download all data locally then upload elsewhere.

3. https://help.dropbox.com/security/privacy-policy-faq#7.-How-...