Good to hear!
I jumped into EndeavourOS (arch, btw), and had a similar experience to you. I’ve had my eye on OpenSUSE, but I’m still enjoying EndeavourOS

It could just do with a UI refresh and maybe some added functionality

That is actually huge ask.
Mumble works in an “engineer brain” kinda way. Cause it has been made by engineers making sure the underlying tech is available to be used in so many scenarios.
Making it work in a “user” kinda way is a huge change.
And it would either make the code really difficult to maintain, or would isolate the power users by restricting the flexibility of mumble.
The fact that mumble is FOSS is absolutely fantastic!

Feel free to fork the project and refresh the UI.
Or sponsored programmers to do this. If there is actually a market, you would be able to overtake mumble. You can even start from their codebase, the license is very permissive (just make sure you credit mumble!)

Yup. parseInt is for strings.
Math.floor, Math.ceil, Math.round or Math.trunc are for numeric type “conversions” (cause its still a float)

Chisel, Rathole, an SSH tunnel with port forwarding, a VPN with port forwarding.
Keywords are “self hosted tunnel” or “reverse proxy over VPN”.

Run a VPS for like $5 a month, your local reverse-proxy tunnels out to the VPS, and your VPS forwards port 80/443 over the tunnel to your reverse-proxy.

A LiveUSB that has memory checking, storage checking, gpu checking along with stress testing of these would be amazing.
Building a new PC? Slap in the liveUSB, check all the components then stress test soak it to confirm its all good

Wouldn’t it be better to have highly available storage for the git repo?
Something like Ceph, Minio, Seaweedfs, GarageFS etc.
Cause git is file system based.

my router and my reverse proxy (traefik) is able to receive the necessary SSL/TLS certificates however

From something like LetsEncrypt?
As an HTTP-01 Challenge? Not an DNS-01 challenge?
Http challenge means that port 80 is accessible from the public internet (because that’s how LE can confirm it can reach your server via the public DNS records, proof of server ownership).
DNS-01 is about proof of DNS record ownership, and doesn’t prove public internet access.

Also, what are you self hosting?
Does it really need to be publicly accessible? Or just accessible by you and people you trust?

If it adds to the content, then it is worth something. So make someone worth something.
If it doesn’t matter, add a random screenshot of kernel code.

The “worth something” doesn’t even have to be financial.
Find a nice image that someone has made which is linux-related, and ask if you can use it & credit the author.
If no, try someone else.

If that’s too much work, use a random screenshot of kernel code …

There are artists out there that have already freely shared some really cool art, that would love to be able to point to publications that they have permitted to use it.
If you have some budget, pay them. Value the time involved.

Just not AI filler BS. I’m not going to see some filler AI art and go “oh yeh, I’m going to use that for X/Y/Z”.
But if I see some cool art, I’m inclined to commission something for an actual use case

You need to control a domain, so LE can verify you are the controller of the domain, then LE will issue you a certificate saying you are the controller of the domain.

For a wildcard LE cert, you need to use the DNS challenge method.
Essentially the ACME client (or certbot or whatever) will talk to LE and say “I want a DNS challenge for *.example.com”.
LE will reply “ok, your order number 69, and your challenge code is DEADBEEF”.
ACME then interacts with your public nameserver (or you have to do this manually) and add the challenge code as a txt record _acme-challenge.example.com. (I’ve been caught out by the fact LE uses Google DNS for resolution, and Google will only follow 1 level of NS records from the root authorative nameserver).
All the while, LE is checking for that record. When it finds the record, it mints a wildcard certificate.
ACME then periodically checks in with LE asking for order 69. Once LE has minted the cert, it will return it to acme.
And now you have a wildcard cert.

So, how to use it on a local domain?
Use a split horizon DNS method.
Ensure your DHCP is handing out a local DNS for resolving.
Configure that local DNS to then use 8.8.8.8 or whatever as it’s upstream.
Then load in static/override records to the local DNS.
Pihole can do this. OPNSense/pfSense can do this. Unifi can do some of this.

How does this work?
Any device on your network that wants to know the IP of example.example.com will ask it’s configured DNS - the local DNS that you have configured.
The local DNS will check it’s static assignments and go “yeh, example.example.com is 10.10.3.3”.
If you ask you local DNS for google.com, it won’t have a static assignment for it, so it will ask it’s upstream DNS, and return that result.
And it means you aren’t putting private IP spaces on public NS records.

Then you can load in your wildcard cert to 10.10.3.3, and you will have a trusted HTTPS connection.

Here is a list of LE clients that will automate LE certs.
https://letsencrypt.org/docs/client-options/

Have a read through and pick your desired flavour.
Dig into the docs of that flavour, and start playing around.

If it’s all HTTPS, consider using something like Nginx Proxy Manager (https://nginxproxymanager.com/) as a reverse proxy in front of your services and for managing the LE cert.
It’s super easy to use, has a decent GUI, and then it’s only 1 IP to point all DNS records to.

DNS and domains are just human-friendly IP addresses.

You only have 1 public IP address.
So, to access different services you need to use different ports.
Or run a service on a single port in front of the other services that can understand the connections and forward the connections to the actual services - known as a reverse proxy. In the case of http/https, there are plenty of reverse proxies that can direct requests based on all sorts of parameters, subdomains being one of them.

If you are just starting out, I’d recommend a docker compose stack and Nginx Proxy Manager.
Learning containers & docker makes everything easier.
NPM is a very easy to use reverse proxy with a nice GUI, so you don’t have to configure CertBot/ACME or learn the specific config language of Nginx.

If you are unsure of domains and all that, you can try it out for free.
Your computer has a hosts file (/etc/hosts on Linux, I think it’s in system32 on windows). This allows you to tell the computer “for the domain example.com use the IP 10.0.0.200” or whatever you want. You need a hosts file entry for each subdomain.
What this means is that you can run up a docker compose stack on your computer and point a bunch of sub domains to 127.0.0.1, use self-signed certs, and play around with nginx proxy manager and docker.
No money spent, no records published, no traffic leaving your computer.
Zero risk.

There are loads of tutorials out there on NPM and docker compose stacks. Probably some close to your specific requirements.

I was aware of kubernetes 6 months ago, but had never used it.
I got a 3 node cluster running in a day, and was learning kubernetes.
The only issues I’ve had were due to hardware failure causing etcd instability, and misconfigured operators generating terabytes of logs leading to pod eviction.

I don’t know what would signify it being production ready. It had all the levers and knobs I needed. I haven’t yet needed to run a sysadmin debug container to poke around the host OS.
It’s also great for learning. If you make a mistake, it’s very easy to wipe and reinstall and get back to where you were.

Talos is great

I do that, until some container has permissions issues.
I tinker, try and fix it, give up and use a volume. Or I fix it, but it never seems to be the same fix

And keycloak has a decent k8s operator, making deployment on a k8s cluster a breeze

Pretty sure that and the White House advert halted the dip the last few days.
Except fElon hasn’t changed, so down it goes!

accessed from the internet

Accessed only by you and close family/friends who you are also hosting services for?
Or accessed by anyone?

“Accessed by anyone” carries more risk.

“Accessed by users you host for”, the risks can be eliminated (well, other than risks from those users) by using a VPN. As in, only the people authorised to be on the VPN can access the services.
Wireguard is the go-to these days.
Tailscale is much easier and free for 3 users and 100 nodes.

If it absolutely has to be “accessed by anyone” I would look into a “reverse proxy over VPN/tunnel” or just straight tunnel style approach like chisel (or crowbar, or corkscrew), rathole, frp, or cloudflare tunnels.

Basically, don’t point a domain at your home public IP and don’t forward ports on your home router/firewall

It’s a server with integrated UPS and KVM console.

The value after the : isn’t in double/single quotes, so it is a literal value. Thus, a float value will be parsed as a float. Whether it is 1E-5 or 0.00001. They are numerically equivalent, but not stringly equivalent.

If you are having errors parsing your JSON, then use a proper JSON library instead of trying to roll your own.

But that’s a stringify method, tho.
JS passes a float to the console. Console prints the float however it wants to.

Just do strict comparison when you want to compare a variable to1e-5.
Cause a string of 0.00001 should be passed through parseFloat (or whatever your language equivalent is) before you compare it to a variable with the value f0.00001

I am using Talos Linux. It’s Linux specially cooked for kubernetes. It’s been super simple and has been very reliable so far.
Also, if I mess something up badly, it’s really fast to get back to a clean k8s install.

For storage, I am using LocalPathProvisioner for fast local nvme storage (I use CNPG to run postgres, which handles clustering in postgres). https://github.com/rancher/local-path-provisioner
There is an issue about backing up PVCs https://github.com/rancher/local-path-provisioner/issues/85

For distributed/redundant storage I use Ceph Rook. https://rook.io/docs/rook/v1.9/ceph-storage.html
Again, super simple to set up.
Docs for backups:
https://rook.github.io/docs/rook/latest/Troubleshooting/disaster-recovery/?h=veler#steps

My current workload is lots of short-lived stuff, so I make sure I have automated and replicable deployment of stuff, so I haven’t dug into backups.
Which limits how much help I can provide.