FreshRSS works well for me, also in combination with Read You on Android.

The request from the other machines go through the firewall and are being redirected, the requests from the NAS are basically trying to connect to localhost, so no redirection here as the requests aren’t leaving the machine.

You’re mixing up two units.

Let’s say your battery has a capacity of 2 Ah (ampere * hours) and your charger outputs 2A (Ampere). This means the charger would need 1 hour to fully charge your battery. Now take a 1A charger, this would take 2 hours to charge the same battery.

Are we talking Apple or apple pie? Because from your post I can’t really tell.

Wait, you update productions systems without running a staging environment? Or even checking the update notes and your installed apps? Also no backups? What kind of business are you running over there?

If setting up TLS is too much work, better stay with a service. Signal is nice.

It really depends on if you need transcoding or not. If no, it doesn’t matter. If yes, check for integrated GPUs on both models and check that it will work as a transcoder for jellyfin.

Kavita works well for me.

The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.

Why would I need a separate router for that? I’d need to configure the main router anyway.

Which display size? How much storage?

Budget?

Sure, if you’d rather like to believe that.

The other bad news: there are so many vulnerabilities on all systems which can be used to gain root-level access, it’s just a matter of time. Also, even future vulnerabilities will be an issue, as the underlying Sinkclose attacks will still work.

Docker image is already updated.

That’d have worked too, yeah.

Ah. Personally I’d do the mounting via fstab to get a consistent path.

How do you mount your volume?

I am unsure about sustainability

In what regard?

Apart from the world of trouble you might get yourself into when doing such things on secured systems, why are you going at it in such a complicated way?

Why not simply use a self hosted file/document storage and sharing solution like Nextcloud or Pydio Cells or something like that? Reachable through standard HTTP(S), which is a lot easier to reach than most other protocols.

I’m thinking 25DB is a hard cap, ideally under 20DB.

I think HDDs are typically around 5-10DB,

Um no. More like 20-25db at idle, up to 30 during heavy seek activity, depending on model.

I run 3x 5400rpm drives in my NAS, and the drives are definitely the loudest parts in the whole build, and are definitely noticeable in the office room.