I run a lot of services on a single old NUC I got for less than 100 dollars. I added some RAM (back then when you could buy some) and a new NVMe stick later when, but since then this single machine could handle all I asked it to do.

That’s the beauty of a memory leak. Even plenty of RAM can get filled up to the brim…

I am also using it and it is really easy to use and looks nice.

Didn’t know that. I agree it is a terrible name, but maybe that’s why it is safe from any cease and desist orders…

Are you maybe looking for something like Revolt or Spacebar?

I am thankful for any input. Maybe it helps someone else looking for a similar thing.

I think the collaborative part means sending PDFs from user to user and maintaining the ability to edit annotations. That may work for many use cases - a lot of businesses may be fine with that when email is still the communication medium of choice.

I have an installation of Stirling PDF, but in my short experiment it had no ability to collaborate on the same document.

Every edit created a new copy of the document downloaded to the user. The annotations weren’t tagged to the individual user and sending different versions of a PDF from user to user is not what I am looking for.

Stirling is a single user software in that regards. I haven’t tested the also mentioned BentoPDF but I suspect it to be the same as it is also trying to be a PDF toolbox like Acrobat. PdfDing has a slightly different approach it might be an option if OnlyOffice does not work out.

I will look into these, do you know if they support collaborative annotations?

Gitlab CI/CD pipelines are my go-to tool. At work we self host an instance, for personal projects I use gitlab.com.

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 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.

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.

Is your server running on UTC? Depending on your location midnight UTC could also be 8 AM and it could be a user with a very regular morning schedule.

Only you can find out which machine is sending this request…