its interesting because even fecesbook has a setting for this
WhyJiffie
I think it depends. when you run many things for yourself and most services are idle most of the time, you need more RAM and cpu performance is not that important. a slower CPU might make the services work slower, but RAM is a boundary to what you can run. 8 GB is indeed a comfortable amount when you don't need to run even a desktop environment and a browser on it besides the services, but with things like Jellyfin and maybe even Immich, that hoard memory for cache, it's not that comfortable anymore.
no, I mean the system has been up for a long time, but the server went down, and connection was lost
well, that is sad. thanks for the info
has it been proven that they alter archived content? haven't heard that before
I've read that somewhere else too, could be
it won't provide that, everything will still autoorun, but known bad things won't get to run
thanks!
do you perhaps also have a solution for hanging accesses to network mounts when the server is inaccessible?
read the man pages. type "man systemd" into a linux terminal, and when finished also read the "see also" pages at the bottom. man systemd.unit is also a "central" page, it says lots of things common to all unit file types.
when you stumble into long parameter lists, you can skip them, you probably won't use most of them. not because they are useless, though, so it's better to at least read the names of all the parameters you come across that way so you have a picture what's available.
skip systemd.directives, but know what it is: a catalogue of all systemd directives with the man page they are documented at. very useful, when you want to find something specific.
"man systemd.special" is special, it's more about its internals, very informational, but relies on preexisting knowledge
what do you use as a prerequisite for the nas A mount? or does it iust keep trying in a loop?
sorry, I think I was wrong. signal/molly only attaches that information to a contact when it already has the phone number that they use for signal.
so unless you keep your phone number visible on signal, or you share your phone number in another way, this shouldn't be a problem.
almost every self hosted service needs a database. and what "another" database? are you keeping separate postgreses for each service that wants to use it? one of the most important features of postgres is that it as a single database server can hold multiple databases, with permissions and whatnot