Weigh your house then step outside and weigh it again. Calculate the difference.

Had to learn it as a kid to get my ham license, now apparently its not part of the exam process for the license. I’d fit right in today because ill be damned if I can remember any of it.

Jesus, you’re trying hard to be a dick, huh. Try harder.

I have to start to learn how to automatically create notes. I’m starting to forget how my systems work together, too. Fortunately when I research something I do it the same way every time so I come up with the same result, then go to implement it and find all the scripts etc that I forgot about that do that job.

I hate the “Microsoft Recall” idea, but damn, I need something like that with an AI to keep it indexed and searchable as it relates to my activities. All self-hosted, of course.

Fedora KDE.

I’m sick and tired about hearing about Zorinn when there’s a dozen excellent Linux distros that aren’t derivative trash that astroturf social media and pass off other Foss projects as their own.

I don’t see this phenomenon. Maybe people suggest those things to use because frankly, they’re a very fundamental part of the self-hosting landscape, and you’re see it as “you must use these”. Use whatever the hell you want and pay the price for doing it the hard way, by all means. But saying people are gatekeeping isn’t the way I see this community.

If you do a zfs list from the Proxmox server command line, you’ll now see a dataset named something like rpool/vm100-data-disk1 and that the second virtual disk in your VM. Now you operate on the virtualdisk however you like, format it with EXT4 or something (don’t use ZFS). It’s still a ZFS volume and Proxmox will be able to snapshot it, replicate it etc, or you could do it manually on the host. But as far as the VM is concerned, it’s a raw disk that you do normal disk stuff with.

deleted by creator

I couldn’t sleep at night if I didn’t have my data backed up in 6 different places. I spent way too many years as a sysadmin to deal with 2 backups.

ZFS mirrors on my Proxmox server with multiple nodes replicating to each other. Replications of those datasets to zfs.rent. Proxmox backup server taking hourly snapshots and doing it to multiple drives. Rotating USB drives on that PBS server. Backups of the data for each VM and each docker container stack via rsync. Borg backup. Multiple Nextcloud clients with each having their file syncs held locally, then rsynced to a secondary drive.

I could probably come up with a couple more that I’ve forgotten I have running. I got burned once and it made me mad.

The files and folders of NC are outside of the database. They are fully browseable in the filesystem. The database is just there for the metadata.

Most of the Erikson ones do this it seems.

I virtualized my OPNsense years ago via Proxmox and put it on HA. I’ve had it failover to another node that blinked out for some reason, and not noticed it for weeks. I’m a complete believer in virtualizing it. I used 2 nics per node and the external NIC is on a switch across all nodes. YOu could use VLANs instead.

Not to mention the snapshots before updates, and restoring via PBS (which I’ve had to do and takes a few minutes). I would never go back to bare metal.

I like Fully_Kiosk on android, but it’s paid.

Eh, I just saw you weren’t meaning a tablet. That’s what most people kiosk on.

The number of kiosks that are stll Windows NT would make you shudder.

I thought it was pretty weird, so I tried again a while later; same result. I checked through issues and couldn’t see anything, I figured it was just me. I tried because NPM was just full of error logs and was having some sort of shitfit, so I blew it out and rebuilt from scratch, now all is fine. But the NPM+ defeated me. I might have to try again just because.

NPM+ didn’t work worth a damn for me. No proxies would forward, I have no clue why and couldn’t figure it out. It was like I was turning knobs that weren’t connected to anything. But YMMV.

Judge someone by the company they keep.

Long ago I learned to stop convincing people to stop shooting themselves in the foot.

It needs to be running on postgres and redis. The AIO is your best bet