EarMaster

That is true for a single person - but in a multiple person household that would mean that everyone needs to carry a copy of their with them. So this mechanism is no replacement for a solid backup of the server somewhere else…

The Bitwarden family plan has been one of the best expenses (if you want to call it that, because it really isn't that expensive) in our family.

Good to hear. Now buy an external HDD or a device of your choice and copy the files there and store it somewhere safe. One backup is no backup.

You may want to change the title and include the word "protection"...

The traffic is really suspicious. Have you by any chance a health or heartbeat endpoint which provides continuous output? That would explain why so little hits cause so much traffic.

It is an open alternative to MS365 developed on behalf of the German ministry of the interior and distributed as open source software.

https://www.opendesk.eu/en/product

If I remember correctly it is not an independent development but it is based on existing software and integrating them to build a consistent service.

I think it combines Nextcloud, Element, Jitsi and some other projects.

The community edition allows me to have multiple sites, multiple users and is way easier to set up. If I ever need additional features like funnels I would need a subscription for both - Plausible is less expensive.

Just a word of warning for everyone: The free self hosted version is heavily limited. I will stick with Plausible which may be simpler but also doesn't want to push me into a subscription.

The free self hosted version is heavily limited. I will stick with Plausible which may be simpler but also doesn't want to push me into a subscription.

Everyone has experienced an AWS / Google Cloud / Azure outage or has had a service - you are happy to use switching to (more expensive) subscription service. That's two things that are not going to happen to self-hosters (except the outage thing, but you can actually do something about it when it happens).

You could use automated testing tools to do the work for you. You define your requirements as individual tests and every input is tested separately giving you a report which tests failed and which succeeded.

Setting aside the funny (if you're not affected) coincidence of AWS being down I have to say this is an exemplary way on how upgrades should be announced, executed and documented. There is a migration guide, but even if you don't read it - in most cases the software will take care of it itself. Well done!