Might reevaluate the "instant" part, then.

(I've been using docker for 7 years or so, and it's always some bullshit like undocumented environment variables or bullshit password limitations or broken smtp implementations or the repo just assuming you are the actual dev and giving no fucking instructions at all or the container shitting itself for no motherfucking reason at random times and you try to fix it and it goes well and then you wake up and it's restarted several times through the night...)

(eyes bulging, hyperventilating)

I... What? Do you know how the past works? And humor, too. Like, just..... What?

I have a ThinkServer with a similar Xeon, running proxmox -> Debian, so I was looking like "huh, interesting" until I saw the internals.

Fuuuuuuuuuuuuuuuuuck all that. Damn it Dell, quit your weird bullshit. It's just a motherboard, cpu, cooler, and ram. Slap in intake and exhaust fans. Figure it the fuck out.

E: and it better have a goddamn standard psu, too. Fuck yourself, Dell. I've seen your shit.

Open hb, edit the affected backup plan, change nothing, okay/save. Happens when you set up a service to be backed up and then uninstall the service.

Because they are wrong. And they need to be shown the error of their ways. You don't get to 150wpm by being nice and casual on the internet, no sir.

I can't possibly see why politics is so polarised

Spoken like a true well-off middle-aged+ white cishet. 'I don't have any problems, so I don't see what the big deal is!'

...you act like you had control over their views at any time in the past, which is hilarious. Staying is simply suffering for no benefit. Now I'm not going to kinkshame, but damn man, you should really find another way to cum; anguish is going way too far.

Me, disabled and home-bound (with the folks): that's great and all buttttttttt

Quick deploy and poking, in order: nicer UI; supposedly compatable (sync) but I couldn't get it working; and no idea never heard of it.

The .env for the compose file is confusing and it slowed my deployment way down, but other than that, it's pretty painless. The variable names are... not clear. Just delete all the sso stuff unless you use it, set a secret and a db password (no special chars, nothing beyond 100 chars, in my testing/struggle; at least for the db), change the url to your fqdn otherwise it will go to localhost when you log out, and disable registration after you have done it yourself. Import/export from linkding to linkwarden (and I assume vice versa) is fine.

puts it in my butt

thumbs up

Me, in response to their response: [citation needed]

I'm all in, as long as the hookers are guys. And gay. And free. And furries. And hung. And kinky. And...

I'm sorry, what were we talking about?

That's the thing about records: they aren't always positive/in the trajectory you are hoping for

That was mine... In the early 00s. And again with a guest speaker... In my advanced marketing class... In the late 00s. I will never forget how that lady sat on a desk, explaining with vivid, passionate excitement and lust, how waiting for your life partner to be your first time is, moans and quivers, so good~

The fuck, Smith, I thought we were going to fuck around and watch movies while you go "make some copies" only to never return, like every other day. The fuck is this shit. Even your own kid in this class is visibly distraught and confused. Poor guy is fucking scarred for life.

Play with my screwdriver daddy uwu

So I have an off-the-shelf nas from synology; while I have two additional servers (ThinkServer, VPS) that are barebones running Debian/proxmox, I haven't moved away from the synology box because it's so... not "easy" but it's like bowling with the gutter guards in place. For example, if you tell the firewall "hey, block everything" it will try, fail to connect to the browser you are using, revert, and tell you. It has a nice web UI that is similar to a standard OS UI. It let's you learn and try stuff, and when things go sideways it's not an evening of combing through forums and pages of documentation. I can, I have, done the 'from the ground up' on the other two systems, but for the syno: why would I build my own box, redo effort - more effort - to get to the same outcome currently? So I will hold onto it until EoL, whenever that will be.

Not to sound like an advertisement, but it does file sharing pretty easily ootb, and you can either set up a DDNS with a subdomain of your choosing, and a list of domains owned by synology (for newbies), or you can use that DDNS system + hook it up your own domain, like MyWebsiteWhatever[.]org. Either way, you can then access your files via a browser, software for win/mac/linux, or from their mobile apps. I also use their photo solution, and have my family pics backed up straight from their phones. Every quarter I make sure that they haven't been logged out (system update / reboots seem to jostle things) and all is well. They have a system for calendar/tasks, as well as for contacts, but I personally have moved away to a direct "radicale" (software name) system, which I think is what synology uses at its core for cal/task/contacts, just adding their gui. Anything else (for my situation) gets a docker container, and this is how I learned about containers. They seem like a black box, but they are absolutely fantastic. Again, great for learning in a controlled environment.

The whole system is very hand-holding, a bit too much so at times. But coming from a "I'm a geek who wants to learn 'proper' network sharing, and this seems to be a nice solution", after researching a few popular options, I think I did well. If you can setup things like a static IP in your router, if you can port forward, and if you're willing to shell out the initial cost for the system (which is overpriced, honestly, but you're paying for the simplicity) and hard drives... you should try it. It's not as scary as it looks. Shoot, if you want more details I can dive in and explain specific stuff, examples, screenshots. Though maybe over DMs so I don't flood the post with unrelated stuff :p

E: autocorrect shenanigans

E2: more detail

Time to add a body to the pile, then

It's more effort ofc, but host your own solution via a nas or something. I have all my shit on one at home, syncing to devices and offering access over the internet, and I know that my shit is safe because I know what the fuck I'm doing, and strangely I'm not trying to fuck myself out of a monthly subscription or something. Never worry about getting flagged by some bot and getting my account purged. Very, very slim chance of a data breach, since the system auto-updates and is secured behind passwords, mfa, permissions on each user. It's my data, under my control, doing what I want and nothing else. And it's freaking fantastic.

This is usually (expected) followed up with... "well, the fuck are you going to do about it, then" and this fuckface decided to pussy out and fuck over 500 people.

So I mean, half right, but that's still a giant red F in my book.

It's okay, it happens to all guys at that age