tobiasd 52bff45b88
continuous-integration/drone/push Build was killed
adjust limit
2026-06-15 14:48:39 +02:00
2026-06-09 13:23:01 +02:00
2024-02-23 11:25:17 +01:00
2026-06-09 14:33:25 +02:00
2025-11-13 05:35:26 +00:00
2026-06-09 14:33:25 +02:00
2026-06-09 13:23:01 +02:00
2024-05-22 10:52:56 +02:00
2026-06-15 14:48:39 +02:00

At FSFE, each staff member used to send weekly timelog reports to a council via email. This instance has been created to automate this process.

Automation Steps

The process consists of several steps:

  1. A dedicated account on our Nextcloud is created, that has access to the timelog.txt files of all staff members.

  2. This account is mounted in a Docker container with help of davfs2.

  3. In the Docker build process, report.sh file is copied into the container. Additionally, gtimelog-utils is cloned so that weekly.py can be used. See the Dockerfile.

  4. Drone builds the container through Docker-Compose using the Drone Secrets.

  5. Every Monday at 02:00, report.sh is executed, applying weekly.py to all timelog.txt files and generating the report from two weeks ago for each staff member. The cron job is set in drone settings.

Run Localy

Docker-compose wants to have the following environment variables:

NEXTCLOUD_URL NEXTCLOUD_USERNAME NEXTCLOUD_PASSWORD

You can either store the values in Drone Secrets or create an .env file for this purpose.

S
Description
Docker VM to centralize gtimelog report generation
Readme 315 KiB
Languages
Shell 88.6%
Dockerfile 11.4%