cato447/challenge_status_tracker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Source challenge status from GitLab instead of Nextcloud

Browse Source 
Read the README.md of every repo in the GitLab challenges group via the
REST API and rework the HedgeDoc note for project tracking: challenges
ready for infra testing first, then status by category and a
category x difficulty grid. Free-text status/difficulty/category values
are normalised; untouched templates and repos scheduled for deletion
are left out of the counts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Casually9790
2026-10-20 16:12:35 +02:00
co-authored by Claude Opus 5.5
parent 7c546ab673
commit e8a04fe415
6 changed files with 423 additions and 291 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ctf-status.timer
+1 -1
View File
@@ -3,7 +3,7 @@ Description=Refresh the CTF challenge status every 30 minutes
[Timer]
OnCalendar=*:0/30
# don't hammer Nextcloud and HedgeDoc on the exact half hour
# don't hammer GitLab and HedgeDoc on the exact half hour
RandomizedDelaySec=60
AccuracySec=30s
# catch up on the last run if the machine was down when it was due