Files
challenge_status_tracker/ctf_status.env.example
T

23 lines
1.1 KiB
Bash

# cp to ctf_status.env and chmod 600 (a plain .env next to the script works too)
# --- GitLab: the group holding one repo per challenge -----------------------
GITLAB_GROUP_URL=https://gitlab.lrz.de/h4tum-ctf/h4tum-ctf-2026/challenges
# fine-grained personal access token, scoped to that group, with
# Project: Read (list the repos)
# Repository: Read (download each README.md)
GITLAB_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx
# --- HedgeDoc: the existing note that gets overwritten every run ------------
# full URL of the note (its permission must be "freely" so an anonymous
# run may write to it), e.g. https://hedgedoc.cit.tum.de/AbCdEf123
HEDGEDOC_NOTE=
# YAML front-matter tags written at the top of the note
HEDGEDOC_TAGS=Logistics, h4tum CTF 2026
# --- deployment repo: --challs keeps <CHALLS_PATH> in it up to date --------
# one clone URL per line for every challenge at Testing Ready or beyond. The
# token additionally needs, on this project: Repository: Read + Repository: Write
CHALLS_REPO_URL=https://gitlab.lrz.de/h4tum-ctf/h4tum-ctf-deployment/ctf-deployment
CHALLS_PATH=2026/challs.txt
CHALLS_BRANCH=main