

IMO, the easiest way to make your system not swap into some disk you don’t want it to is to not enable any swap partition on that disk.
If it’s using that much RAM for cache, it will survive not having a swap with a minimum impact on performance.


IMO, the easiest way to make your system not swap into some disk you don’t want it to is to not enable any swap partition on that disk.
If it’s using that much RAM for cache, it will survive not having a swap with a minimum impact on performance.
If you use moodle, it has a plugin for that, with instructions.
If you don’t use moodle, you may want to check the instructions on the plugin anyway.


You think you are tacking ‘real’ issues with your servers, but to the average user you seem just as crazy as a guy with a basement full of beans and piss jugs, screaming about the government is watching us constantly.
The government is watching us constantly. There’s no doubt about this and if you think it’s not, you are the crazy one living in fantasy land.
At the same time, how do you think a basement full of beans would help? The entire path from “the government is bad” to “therefore I’ll have a hole full of food where I can live by myself for years” is dumb magical thinking that can be shown to not work by simply looking around or reflecting about oneself for a second.
There are many valid reasons to be concerned about a disaster. And yet nobody doing your traditional prepping for anything larger than a tornado deserves respect.


The added features made it harder to deploy, came with some bugs, and overall traded a simple design for community-oriented features that IMO were a negative value overall.


IMO, the Gogs dev was correct. If you look at that community input and what Gitea became, I was glad to use the version that rejected it.
But I don’t know how it compares with Forgejo.
You test your backup by recreating your system, either in a local environment or in some cheap simulated one.
It’s even better if you write a manual with the steps you needed. And try to follow (and update it) when you do it again.
I figure the most bang for my buck right now is to set up off-site backups to a cloud provider.
If you don’t have the budget for on-premises backup, you almost certainly can’t afford to restore the cloud backup if anything goes wrong.
Then I started reading about backing up databases
Go read the instructions for your database in particular. They are completely different from each other. Ignore generic instructions.
now I’m configuring a docker-db-backup container
What is perfectly fine. But I’d first look how this interferes with the budget you talked about earlier and if it wouldn’t be better to keep things simpler and put the money on data replication.
Either way, if your budget is low, I’d focus a lot on making sure you have the data when you need to restore, and less on streamlining the restore procedure. (That seems to be the direction you are going, so yeah, I’d say it’s good.) Just make sure to test the restore procedure once in a while.


Enough to make a RAID 6. As few as possible.


That’s just sloppiness.
The information that familiarity gives you is “WTF does this field means”, and it’s the only thing that’s actually there. How you get a value and how a value is formatted are things no amount of expertise will save you from having to tell the computer, and thus you can’t just forget about.
(And let me guess, the software recommended install is a docker image?)


AIs have been capable of doing this for ages already.
It just falls into the set of useful stuff that LLMs trained as chatbots suck at because they had the useless goal of convincing people they are smart.


DDG already sends your search query to third parties. What they don’t send is your identity.
(Or, at least they say they don’t, whether you trust them is your option. Any 3rd party can betray your trust.)
Anyway, that image implies an in-house implementation.


It’s neither. Why do you expect they calculating an answer to have any impact at privacy?
Hum, no. The last thing I need on the world is a piece of non-working hard to maintain software.
I’d write something before trying Nextcloud again.
Personally, I’d really like if it could have different users on its management interface, with their own file shares.
It’s understandable why they don’t bother, but I would like to share my NAS without running several instances.
I’ll second people here in pointing that you are better allowing calls from your family during the “Do Not Disturb” than trying to set-up things not to call you during that time. Your phone almost certainly has a setting that allows “favorite contacts” or something like it.
It has a better configuration orthogonality :)
Yeah, that’s not a good reason.
It’s much easier to authorize a key than to input your password on every kind of interaction.
This is the internet. If you poke the bear, somebody will come-up with a completely reasonable use case of password authentication that happened once somewhere on the world.
If you don’t have any good reason not to, always set your SSH server to only authenticate with keys.
Anything else is irrelevant.
Oh, sure, the bloat on your images requires resources from the host.
There is the option of sharing things. But, obviously that conflicts a bit with maintaining your environments isolated.
Look at the anubis challenge algorithm, reimplement it, publish it for the rest of your government organizations.