I hope someone gives you a good answer, because I’d like one myself. My method has just been to do this stuff little by little. I would also recommend calibre web for interfacing instead of calibre. You can run both in docker, and access calibre on your server from whatever computer you happen to be on. I find centralizing collections makes the task of managing them at least more mentally manageable.

You might want to give an idea of the size of your library. What some people consider large, others might consider nothing much. If it is exceedingly large you’re better off asking someplace with more data hoarders instead of a general Linux board.

Hah, that sucks. My bank app let me log in without a password on my new phone just using the new fingerprint on the new phone, because I transferred the app from the old phone. Course, they recently limited cross account transfers to $100 because they’re seeing lots of fraud. No shit, right?

I had an account with a bank that got bought. Always used the app, which worked fine, but I needed some document I could only get from the website. Go to log in and it gives me all sorts of weird errors. Support made me reset my password, all that stuff. I figured it out. Old bank would let you log in with email or username. New bank only let you log in with username, except it had dropped old bank’s username and put the email in the username field in their database. The website scrubbed emails from that field, and so it submitted a null username. The app didn’t l, so it let me log in. Weirdest issue I’ve ever had with a service and actually figured it out.

I believe solokeys are open source. I use a solo v1 for sudo, ssh, and two factor websites. They either went out of business or are basically defunct as I understand it, but you can pick them up on crowd supply. I wouldn’t get the v2, supposedly they had problems and that’s why they shut down. You likely won’t see updates, but they do function for what you’re looking for. There are some that are shaped like a small thumb drive and some that sit almost flush with a USB port. Some have nfc, which is useful for phones. Buy at least 2 though, and register both for everything, because you don’t want to lock yourself out of something.

Everyone wants constantokra, but only a select few can achieve it.

They glory in the bounty of food. I went to a Cuban restaurant with a friend who was vegetarian. The staff just flat couldn’t understand the concept. Why wouldn’t you eat meat if it was available?

Thank goodness I had a newer monitor then, because I would definitely have toasted several.

This is going to get so Florida, so I’m sorry. Most of the people I know who carry daily carry guns without safeties, so that just wouldn’t work. Also, it’s literally a mark of distinction between “responsible gun owners” and irresponsible ones that before the alcohol comes out all the guns are made conspicuously safe, unless the person is a designated non drinker. They would take on the unspoken responsibility of being armed and vigilant for the rest of the group. This will happen discreetly in mixed company, but likely conspicuously if everyone present carries a gun.

And anyone committing the faux pas of calling a magazine a clip would get a polite correction, and if repeated they wouldn’t be invited next time.

Unironically yes.

I’m so divorced from normalcy I have no frame of reference. Do normal people who don’t do this stuff for a living use Linux now, outside handheld gaming devices? I figured they just used whatever came on whatever device they wanted to buy.

Did you ever dual boot Linux and windows, and also have VMware installed in both so you could boot the other one from inside whichever you had booted? Because I spent an insane amount of time screwing around with that for as excruciatingly slow as it was back then.

You never know when you’ll need to install period Linux on an old piece of hardware.

I think you need to qualify that having used or tried Linux in college was normal in the 2000s for someone in computer science or engineering, or basically my fellow undiagnosed autistics and autistic adjacents. In my experience it was fairly normal in college for most people to have trouble operating a basic word processor, and they would not have had any idea what Linux was at all.

“mailing list and Usenet support”. Yeah. If you’ve ever looked up some weird issues and the only thing that you can come up with is some Debian message group that looks like it was typed on a typewriter, is extremely difficult to follow the response chain, and is apparently from before Y2K… That’s what it was like to run Linux back then.

How wrong did you have to be to break your monitor? Because I’m positive I got it very wrong a whole lot of times and never managed that.

There’s not nearly enough butter on that toast, not enough eggs, and where’s the sausage? In Florida the breakfast gun goes on the dominant side with the grip out. Once alcohol is served the slide will be locked back. In particularly liberal circles the magazines will also be popped out. We aren’t savages.

But it’s the one you deserve.

Yeah, and I assume future me will be even dumber than present day me, so I try to make it really easy for him to find out what he needs to know.

Another good tip is to put timestamps and increase the length of your bash history. That way when I log in half a year from now I’ll know what I was up to.

All of your issues can be solved by a backup. My host went out of business. I set up a new server, pulled my backups, and was up and running in less than an hour.

I’d recommend docker compose. Each service gets its own folder inside your docker folder. All volumes are a folder in the services folder. Each night, run a script that stops all of them, starts duplicati, backs up to a remote server or webdav share or whatever, and then starts them back up again. If you want to be extra safe, back up to two locations. It’s not that complicated if it’s just your own services.

There’s no forgetting where I have something hosted. If I ssh to service.domain.tld I’m on the right server. My services are all in docker compose. All in a ~/docker/service folder, that contains all the volumes for the service. If there’s anything that needed doing, like setting up a docker network or adding a user in the cli, I have a readme file in the service’s root directory. If I need to remember literally anything about the server or service, there’s an appropriately named text file in the directory I would be in when I need to remember it.

If you just want a diagram or something, there are plenty of services online that will generate one in ASCII for you so you can make yourself a nice “network topology” readme to drop in your servers’ home directory.