About a year ago I created a simple complete project: garage-inventory. It's a Github pages repo that uses github.dev to create .md files which when deployed show up on a web url.
I created QR codes to those URLs so that I could see what was in a box and using grep / github.dev could find what boxes things were in. It's serverless, it's simple, and it's been working great.
Today I'm going to try to deploy shelf.nu using #flyio #libreops
I finished configuring my Roku replacement box last night, and put it into service. It's working great!
I almost said "finished tweaking", but, really, am I ever finished tweaking my tech?
Turning an old small form factor PC into a replacement Roku! Come on by, if you'd like. :)
Why does #Nextcloud timeout (HTTP 504) before and after a patch version update?
I can't seem to get it to produce more information than this cryptic error message. Some pointers would really help!
2023/03/28 19:59:50 [error] 20804#0: *1 upstream timed out (60: Operation timed out) while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: mycloud.example.com, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php-fpm.sock", host: "mycloud.example.com"
running PostgreSQL 14.5, Nextcloud 24.0.10.1, PHP 8.0.28 (FPM)
When Discord announced its LLM nonsense, one of the "servers" I'm on migrated to Guilded, knowing full well that it was now owned by Roblox. They figured, correctly, that it was the only available option for hosting the large number of people, and the significant configuration changes that they required.
I've been feeling a bit hopeless about that. Then, when looking through my old browser tabs, I found these:
https://revolt.chat/
https://fosscord.com/
So... there's hope. :)
So, the first build went okay, but then I realized I had not updated the references in the #octoPrint flake for the 23.05 version of my base operating system.
Then, there was no "23.03" nixpkgs branch, so I switched it to "nixpkgs-unstable" and am trying another build.
Doing 61 instead of 350+ build steps, so there's some reuse going on.
Reworking some new(er) computers for my kids, and I once again have am LIVID with the useful features that have been removed from the Microsoft Family setup, and with how badly authentication data (passwords, pins, etc) update.
I didn't think anything could be worse than AppleID, but holy crap, I was wrong.
Found the solution, it was in the wiki and helpfully named exactly like one might expect: https://nixos.wiki/wiki/flakes#NixOS
That said, the next step is to get it pulling in the #OctoPrint flake, which apparently can do URLs but that isn't working for me ("error getting status, not a directory") so we've pulled down a local copy and have successfully used the nix flake metadata
command from there.
Next, doing some edits so that the magic numbers aren't clashing.
Just gonna mention that it's taken seven hours from the start of this #LibreOps dive into #NixOS and #NixFlakes and most of that has just been to get the basic functionality working. For someone without decades of tech background, this would be tantamount to impossible. I think about this a lot when working.
#nixflakes #nixos #libreops #octoprint
Cracked open the packaging on one of my small hoard of new SD cards for this, then realized that the print server already had a card in it, and apparently an OS.
Booted and logged in thanks to the authentication card my past self left for me (last login over a year ago, no memory of this), and discovered that it was an empty OctoPrint install, seemingly never connected to the printer, but with one or two things set up like the old (Robo3d R1+) printer.
Attempting to update via the web interface resulted in "everything up to date" even tho it's all from 2020, so looks like I have two SD cards to play with on this.
The rabbit hole of "find correct OS image to install" is convoluted by the myriad "this is outdated" warnings that scatter the hardware page on the wiki: https://nixos.wiki/wiki/NixOS_on_ARM#NixOS_installation_.26_configuration
There's also the side quest of getting Balena Etcher working on the workstation, since yes dd
does work but I'd rather verify on write, thanks: https://github.com/NixOS/nixpkgs/issues/153537
This is what #LibreOps looks like. Poking the rabbit hole, seeing how far down it goes, and sometimes throwing a bandaid across it and hoping your future self doesn't fall in too deeply whenever the patch rots through in the future.
I've upgraded from an iPhone 6S to an iPhone 8, and my youngest son now has an iPhone 7 for his first phone.
My daughter bought an iPod 5th gen on eBay to see what she could make it do.
I've done something right as a Dad. #LibreOps
TIL bash strict mode(s): http://redsymbol.net/articles/unofficial-bash-strict-mode/
anyone around here running #nitter on an arm device, getting segfaulty errors, and any ideas how to fix those?
the segfaults only happen on user profiles, not searches or individual posts 🤔
Armbian, a linux distribution for raspberry-like devices that are not raspberry pis, is looking for contributors. there are many things to be done that are rather low threshold, so give it a look, if you're interested how such things come together: https://fosstodon.org/@RTP/107197357437000676 #libreops
Fans are in! The PeerTube server hardware is ready to deploy! That feels good. :)
On the recommendation of H-Mods, I have ordered some upHere case fans. We'll see how they hold up. :)
New (10 year old) power supply installed and working. Drives are powered, and I'm now able to finish testing them.
The one I was planning on using for the OS is unresponsive, so I'm going to use a spare 256GB NVME drive with a NVME-to-PCIE adapter.
I may have an unreasonable love of adapters.
And the power supply blew out the LED power on the gaming case. Like, fire traveled up several of the thin wires. It's been a LONG time since I've seen that.
So, it needs fans and a new power supply. I think it's going to go back to dust-collecting until I find some discounted goodness.
Finally moved that used power supply and motherboard into the secondhand case for my PeerTube server.
The case is new-ish, and meant to be a gaming machine. It has a glass side and places to tuck the hard drives away, out of sight.
Meanwhile, the motherboard has HDMI, DVI, and VGA ports onboard. Oh, also a PS/2 port.
It's a wonderful disjointedness, in my oh-so-humble opinion.
I was excited when my SO asked if I could setup a NFS for her to archive a lot of her older video and design work. However, it dawned on me soon afterword that my little hobby NAS was no longer so 'hobby'. So finally setup some automatic offsite backups.
I decided on restic going to a b2 bucket, triggered with a systemd timer. Seems to be working great so far.