julien/apf_portal

Fork 0

Files

T

History

Julien Gautier 1d8de3365f

CI / commits (pull_request) Successful in 3m51s

Details

CI / scan (pull_request) Successful in 4m13s

Details

CI / check (pull_request) Successful in 4m24s

Details

CI / a11y (pull_request) Successful in 3m49s

Details

Docs site / build (pull_request) Successful in 3m51s

Details

CI / perf (pull_request) Successful in 6m54s

Details

docs(setup): make fail2ban opt-in in 70-hardening.sh

Three branches now: (1) already running -> skip; (2) installed but
stopped -> prompt to enable+start; (3) not installed -> prompt to
install+enable+start. Each decline path logs `(user choice)` so a
re-run doesn't surprise the dev with a different state.

Reasoning: some corp environments already ship brute-force protection
at the network layer (ACL / corp firewall / appliance). fail2ban on
the host is then redundant and can be the wrong layer to debug from
when a rule misfires. The other three hardening steps (UFW,
sshd lockdown) were already prompt-gated; fail2ban was the odd one out.

Table descriptors in the main doc + setup README updated to make
each sub-step's prompt posture visible.

2026-05-24 19:59:50 +02:00

.vitepress

fix(docs): cap vite below 7 (rolldown-vite) and pin mermaid transitives (#161 )

2026-05-15 23:57:57 +02:00

decisions

docs(adr): accept ADR-0026 + ADR-0027 (#219 )

2026-05-24 16:58:39 +02:00

setup

docs(setup): make fail2ban opt-in in 70-hardening.sh

2026-05-24 19:59:50 +02:00

architecture.md

fix(portal-bff): align admin entra role name with Portal.Admin (#145 )

2026-05-15 10:33:54 +02:00

development.md

docs(development): refresh after phase-3a + add topology / trace diagrams (#160 )

2026-05-15 23:08:50 +02:00

index.md

feat(docs): vitepress site for docs/, mermaid rendering, ci build workflow (#154 )

2026-05-15 19:14:14 +02:00

README.md

docs(development): add observability dev-loop section (#73 )

2026-05-10 02:14:46 +02:00

README.md

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, observability dev-loop (Jaeger UI, log ↔ trace correlation), 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.