2,822 karma · joined September 19, 2017
And I use RHELlikes (Alma/Rocky) in my homelab just cause its similar to Fedora and Red Hat's documentation is much better than reading random blogs on how to do stuff on Ubuntu/Debian.
I use my oracle free servers (and one paid vps on hetzner) as automatic cloud fallbacks if my homelab is inaccessible over the internet for some reason. Which means I fall in the underutilized category as most of the time workload is under 2%. So I "fake" work to prevent reclaimation by oracle and its worked well so far.
``` # Oracle Cloud reclaims idle resources # https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier...
- name: Create cronjob for minimum CPU utilization
ansible.builtin.cron:
name: fake work to prevent re-claimation
special_time: hourly
job: timeout 30s sha1sum /dev/zero
```Otherwise poeple would just
- buy 51 % stake - run the company into the ground - announce its bankrupt - at the auction buy back IP for pennies on the dollar - start new company with previous IP, same domain name, same servers etc
Also if there was an auction, what prevents Google, Meta, MS, Amazon, etc from buying the IP instead.
You can use any container registry (including self hosted) with docker and it will work. Last I checked, you cannot use any other repo at all with snap without recompling it to add support for your snap repo.
Dall E was unrivaled until stable diffusion came along, OpenAi won't be a monopoly soon.
Or host vaultwarden on your homeserver and access it only through wireguard/nebula self hosted VPN.
whatever Google and Facebook use internally.
Command line software does show up in CLI, just not by its short name. You have to use the fully qualified app name - com.xyz.whatever. You can make an alias if you want.
> Even worse, while there is an option to install things in the user's directory only (so i can make a separate user to try some things that i can easily delete later) not everything installs with that options and wants root access to pollute the rest of my system.
Are you talking about flatpak install --user ? Yes youre right some apps might not work with it but how is that any worse than traditional packaging.
Flatpak isn't perfect and I prefer distro packaging over everything else but it isn't feasable to have distro packaging for everything - not with the strict packaging rules most distros have atleast.
But out of snap, appimage and flatpak I'd go with Flatpak.
Or you can use cloudflared or another one of ngrok's competitors.
Ex: Nitter operates without official APIs.
An operator (or its custom resource) can be configured by Kubernetes YAML/API and its upto the creator of the operator to specify the kind of configuration. If the operator creator did not specify options to set cpu/memory limits on the pods managed by the operator, then you can't do anything. You have to add that feature into the operator and then make a pull request and wait for it to be upstreamed.
Or fork it instead. Same thing for helm charts (except forking and patching them is easier than forking an operator).
You lost me there. Buck/Blaze aren't perfect but configuration was never an issue.
Moon like it is currently is a glorified task runner.
Paying for EKS just to use its API to provision and manage other AWS resources is an interesting idea, but not something I'd use in production.
Any resources for this ? Most books I've read/seen are either about Linux kernel internals or using userspace Linux. I'd like to know more about what actually goes into making a complete usable distro.