I recently set up something similar to this. I can’t comment on your specific hardware, but I was very frustrated with the limitations of TrueNAS and ended up using Debian and Cockpit with BTRFS for the drives.
I started with two 18TB drives with no RAID, and have since added two 26TB drives with everything’s using RAID1 and ~45TB of usable storage. Converting and adding drives was very simple, but also time consuming of course.
I’m pretty sure any distro using GNU software would be disqualified, so maybe Alpine?
That’s awesome, you’re one of today’s lucky 10,000.
It supposedly had something to do with calculus and the ratio between the diameter of the inner most groove to the diameter of the outermost groove being optimal at that size, but I’m not sure how much of that is genuine or just marketing. I’ve also heard that the larger hole is better for the mechanisms in jukeboxes.
The adapter does not affect the speed of the turntable, and you would still need to flip the switch on the record player to 45 RPM. These physically smaller (7") records were commonly referred to as singles because they would hold a single song per side.
The larger (12") 33 1/3 RPM records had a smaller spindle than 45s, which meant you would need to use an adapter like the one pictured to play a 45, as demonstrated in the video shared by @thermal_shock.
Since 33s were physically larger and played at a slower speed, you could fit much more music on each side of the disc. That’s why those discs would be used for entire albums, and were also commonly referred to as LPs (Long Plays).
Let it rip!
That’s not really all that special or unique. There are lots of things that many people would instantly recognize that others would have never seen before.
45/33 1/3 RPM records might be well within your wheelhouse, but would you recognize a 78 RPM record, or an Edison wax cylinder at first glance? How about the image below?
Pfft, those are still maintained (Haiku and ArcaOS respectively) and so corporate man.
TempleOS all the way baby. Nothing is more powerful the the almighty HolyC.
Holy shit I lost it after Material UwU. The system requirements and FAQ (including a famous Torvalds quote) were excellent highlights as well.
Happy to help!
You can find a bit more information at the URL below, and feel free to message me if you run into any issues getting it set up.
https://letsencrypt.org/docs/challenge-types/#dns-01-challenge
Cheers to your journey so far, and to your continued success!
You can absolutely do free SSL certs with Let’s Encrypt without exposing your infrastructure to the internet. Just use DNS based validation instead of HTTP, copy the required TXT records to your domain as instructed, wait for any cache/TTL of any old records to expire (generally 1-2 hours by default), and finally complete the validation.
You’ll need to renew the certs every 3 months, which could be annoying if done manually. If your Registrar has a decent API, writing a script could be a fun automation project. Alternatively I can also send you scripts that I used to use for that purpose.
As a sanity check, I just completed the same setup that you described (Ubuntu Server 24.04 running in a Proxmox VM, Domain name pointing to a CNAME that points to the Dynamic IP, using the installer script, enabled CrowdSec, etc.), and everything worked out of the box. A couple of things I noticed that would also be worth checking now that I’m more familiar with this specific setup are:
dig pangolin.mydomain.com or dig @1.1.1.1 pangolin.mydomain.com should show the CNAME that points to the A record.I hope that helps!
The script should take care of that config, but it’s something to check just in case there was a typo or anything else like that.
Did you check to make sure the DNS records are resolving properly?
According to the docs, you should be using UDP port 51820 (unless you changed the port in the docker compose file).
You should also check the dynamic config file to be sure that it’s using the correct domain name. See this page: https://docs.fossorial.io/Getting%20Started/Manual%20Install%20Guides/docker-compose
If you’re still having issues, make sure the containers are running with docker compose stats and check the logs with docker compose logs -f. It might also be worth checking the domain name to be sure that it’s resolving to the correct IP address, both locally and externally.
No worries! Yes I’m absolutely still interested, and I have the optiplex set aside for you.
Abcde (pronounced AB-sid-ee) was certainly memorable if nothing else.
I currently run it with Keycloak for Auth and previously had it behind a Nginx Proxy Manager reverse proxy, but have since switched to using a Cloudflare tunnel.
It works great and allows me to provision limited and controlled access over various game servers to admins of those servers. They can access what they need and nothing more, and only on the servers that they have been granted access.
I use Apache Guacamole, which works great for just about any kind of remote access and has a dead simple to use Docker Container.
It supports folders, copy/paste, uploading/downloading files, multiple open connections at once, and alternative mouse modes for touch screens. Best of all, it’s completely free and open source.
Imagine if OP asked: “I want to repair/maintain my own car, but I don’t want to open the hood or get under the car. What are my options?”
Obviously there would be some options, but those options would be very limited and not ideal. This is very similar. Self-hosting, like self-repair of a vehicle, requires some foundational knowledge and understanding of your specific hardware, usecase, and needs, as well as the knowledge and ability to bring those things to fruition. There is no single universal answer that applies to everyone, but those skills can be acquired by anyone.
I don’t think self-hosting is any more doomed than self-repair of a vehicle. It’s certainly not for everyone, but it can be satisfying, rewarding, enjoyable, and generally optimized for those who choose to participate.
They absolutely did exist in the 20th century, but they were much heavier and bulky, used resistive touch screens, had awful battery life, and were understandably very primitive compared to modern tablets.