So why would this need docker at all?

Thanks so much for mentioning this, trying it out now

Not at all

One thing that hasn’t been said in this thread is the following: Do you trust your router? Do you have an isp that can probe your router remotely and access it? In those cases, you absolutely need a firewall

Same, always eorked great for me

Not a single app, not minimal dependencies. It’s a file that gets processed and creates many gigabites of leftovers, with an enormous runtime and piles of abstractions

Unless you are a business with millions of users, I would be really skeptical of redis improving performance. At the end of the day, any simple KV store can replace it. It’s not like postgres where having sqlite in it’s place means not only a different performance profile, but also different semantics, sql dialect, rpc protocol, etc

I don’t know but usually uk websites are the worsts of the bunch

No such thing in their website from europe

Bought only the nas hardware, no software or enclosures with OS from the and had no problems

What is it? Why do you find it useful?

Dbeaver

I ditched nix and install software only through portage. If needed, i make my own ebuilds.

This has two advantages:

• it removes all the messy software: i am not going to install something if I can’t make the ebuild becayse the development was a mess , like everything TS/node
• i can install, rollback, reinstall, upgrad and provision (configuration) everything using portage
• i am getting to know gentoo and portage in great details, making the use of my desktop and laptop much much easier

It’s sad how self contained now means “only” one docker image

It syncs my extensions, except for mobile the ones that aren’t available (obviously)

This is very cool.

I an slowly building my own syslog server with visualization, but it’s cool to see new stuff on the block.

I have always been wary of big commercial services like kibana, grafana, etc…

The only good reply in the thread. Thanks for saying this

It is unrealiatic, that in a stable software release there is suddenly, after you tested your backup a hard bug which prevents recovery.

How is unrealistic? Think of this:

• day 1: you backup your files, test the backup and everything is fine
• day 2: you store a new file that triggers a bug in the compression/encryption algorithm of whatever software you use, now backups are corrupted at least for this file Unless you test every backup you do, and consequently can’t backup fast enough, I don’t see how you can predict that future files and situations won’t trigger bugs in a software

Going unmaintained is a non issue, since you can still restore from your backup. It is not like a subscription or proprietary software which is no longer usable when you stop to pay for it or the company owning goes down.

Until they hit a hard bug or don’t support newer transport formats or scenarios. Also the community dries up eventually

As long as you understand that simply syncing files does not protect against accidental or malicious data loss like incremental backups do.

Can you show me a scenario? I don’t understand how incremental backups cover malicious data loss cases