Offen VS docker-volume-backup

Offen: https://www.offen.dev/ For a simple reason: They are opt-in exclusively, and are the only analytics tool that offers users the possibility to review their collected data in the "Auditorium", and also allows them to delete everything.

Happy cake day. Yeah, nowadays there are so many analytics variants out there: Swetrix, Plausible, offen, count.ly any many more.

Offen’s main product is web analytics, which is quite unique if you ask me. The analytics tool is a core requirement of any commercial website out there, as it provides many KPIs to define marketing success. Not only that, analytics can help you target your services to the right clients, increasing your overall income.

Obviously, the development of Offen is not finished with ther current v1.0.0 version. We will continue to maintain the project and adapt it to new requirements. For this we also need your support. Continue to test and install Offen latest releases and share your experience with us.

Statistics about the location of visitors had been on our to-do list for a fairly long time. Yet implementing it in a way that met our privacy standards proved to be a veritable challenge. After careful consideration and intense research, we finally decided on an approach based on time zones.

Offen is a fair and lightweight alternative to common web analytics tools. It’s self hosted software and all code is available at the offen/offen repository on GitHub. In this constellation, feedback and participation is especially important for us. In this article we’d like to share what we do to make our repo friendly and welcoming towards any kind of contribution from the community.

Docker is an ubiquitous tool for us while building Offen, a fair and open source web analytics software. It is foundational for our development setup, but we also use it for deploying our own Offen instance to production.

I am interested in coming up with a backup plan before I get too invested in this setup. I found the docker-volume-backup project that looks like it might be a possible solution. However I'm not sure how to implement it using docker swarm since I am new to all of this. I would be interested in learning what backup solution you use for your docker swarm servers.

How do people usually backup their self-hosted docker services using postgres? I have been using docker-volume-backup [0] and just saving the postgres data directory, but I've found it requires a minute of downtime to backup properly.

[0] https://github.com/offen/docker-volume-backup

Offen: https://github.com/offen/docker-volume-backup

To solve points 1,2 i 3 I think it would be best to make the copy by stopping the container first. I've been looking for utilities and I've found some like offen/docker-volume-backup. Again, the disadvantage is that you have to configure everything (mount points, files, users, passwords...) manually for each container, so it is very easy to forget to create the backup of one of them. Also, the scheduling would not be centralised, so the backup wouldn't be run sequentially container after container. I've searched a lot, but I haven't found any good alternative. How are you dealing with the backup of containers?

Since I'm using docker rootless, I've run into issues using convenient solutions such as offen. These solutions don't work in a rootless context due to file permissions. The user in the offen container cannot read some directories owned by other containers. This is usually an issue with databases.

FYI this looks like the actively developed version of that utility: https://github.com/offen/docker-volume-backup

You should have backup OS and data but using a separate backup jobs. Backup OS drive using Timeshift or Veeam Agent. Backup Docker server's containers using Offen or Borg. OS backup would allow you restore operating system while data backup would allow recover files.

There is the image docker-volume-backup that allows you to make backup but depending on the situation (databases, ...) it is not necessarily the best solution