What is “Make”? Hard to Google name.

Have you considered open sourcing you self built solution?

I seems a long time ago, I build the same thing as you. For templating I used https://github.com/christopher-ramirez/secretary and as “database” I used Google sheets. Still use it at work.

It never was really user friendly so I am looking to replace it. That is also the main issue with your self build solution? Or are there other issues as well?

I didn’t know about Documint. Looks interesting, will check it out, thanks 👍

Today’s German lesson:

• abholen - to pickup
• Ort - place/location
• Abholort - pickup location

I am still waiting for a localized templating engine, so it is €Payment

While I do see a difference between those two “incentives”, they are not that different to me. Both are about the general economic conditions which a company uses to determine where to invest. Also in both cases the conditions are influenced by politics, and shaped by financial policies.

[…] there is no incentive for companies to go and open their doors in east Germany […] They are building modern factories with high automations and are getting massive incentives to do so.

Which one is it? No incentives? Massive incentives?

1. So, you do want to run rsnapshot on the Borg repository (the destination to which is backed up)? Both rsnapshot and Borg keep a history, so you are keeping a history of when the Borg repository had which history. This will not be particularly efficient nor “as intended”.
2. be aware that Borg does incremental backups on file chunks, while rsnapshot works on whole files. So if a large file changes, rsnapshot will duplicate the storage used.
3. a Borg repository is more like a database of chunks (similar to git), while rsnapshot recreates the original backup data.

According to https://borgbackup.readthedocs.io/en/stable/internals/data-structures.html the repository storage consists of 500mb files. So using rsnapshot on those, will not be work as you want it to.

It depends on the use case. The most common security issue I have seen with docker is on Linux desktop systems: docker deamon runs as root and user wants to use it to test all kinds of containers. So they make the docker socket accessible to the user, to lazy to use “sudo docker” every time… Having access to the docker socket means having the same permissions as the one running the daemon: root . Your browser effectively now has root permissions. At this point you could just login as root to your desktop.