Julien Gautier
7adc6e33f5
`gitleaks/gitleaks-action@v2` is now paywalled for organisations: the action errors out with `🛑 missing gitleaks license. Go grab one at gitleaks.io and store it as a GitHub Secret named GITLEAKS_LICENSE.` Worse, it cannot reliably detect personal-vs-org on Gitea (the GitHub API contract differs), so it defaults to license enforcement and the scan fails. The gitleaks binary itself remains MIT-licensed and free. Mirror the pattern we just adopted for Trivy in #45: drop the wrapper, install the binary directly via curl + tar from the GitHub release, run the CLI. This: - removes a third-party action dependency we did not need; - pins the gitleaks version explicitly; - harmonises with the Trivy step that lives next to it. Apply the same change to `.gitea/workflows/security-scheduled.yml` in the same PR — it had both broken integrations (`trivy-action @master` plus `gitleaks-action@v2`) and was waiting silently to fail at next Monday's cron. Per-PR gitleaks scan uses `--no-git --source .` (working tree only) since the scan job uses a shallow checkout; the weekly scheduled job switches to a full clone (`fetch-depth: 0`) and runs gitleaks in deep-history mode (default), which is the value-add of the scheduled job over the per-PR gate. `--redact` is added on both invocations so any matched secret is masked in the CI log itself (no leak via the log artefact). Also drop `cache: 'pnpm'` from `actions/setup-node` in the scheduled workflow — we already removed it from ci.yml in #8 (the act_runner cache server is unreachable from job containers; every restore burns ~2 min ETIMEDOUT for zero hits). Consistency.
Documentation index
This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.
Conventions
- Documentation is written in English.
- One topic per file. Group related files into a folder when there are three or more.
- Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
- For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.
Sections
Daily development
- development.md — repo layout, prerequisites, initial setup, daily commands, dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.
Architecture
- architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.
Onboarding & environment
Setup guides for new contributors:
- setup/01-wsl-terminal-setup.md — modern WSL terminal (Zsh + Powerlevel10k + CLI tools)
- setup/02-dev-web-stack.md — Node via nvm, pnpm via corepack, Docker
- setup/03-angular-nx-monorepo.md — Angular + Nx monorepo bootstrap
Operations & runbooks
Empty — to be populated when we deploy.
Security, performance, accessibility
Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.