senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
veza/docker/haproxy/certs
History
senke 98ee449f42 chore(cleanup): untrack debris pre-BFG — audio, PEM, screenshots, reports 
Phase 0 (J2 cleanup) of chore/v1.0.7-cleanup branch. Pure index removals
before BFG history rewrite. No working-tree changes, no code touched.

Removed from git index (still on disk):
  - 44× veza-backend-api/uploads/*.mp3        (audio fixtures, ~200MB)
  - 23× root PNG screenshots                  (design-system, forgot-password,
                                                register, reset-password, settings,
                                                storybook — various prefixes)
  - 1× docker/haproxy/certs/veza.pem          (self-signed dev cert, regen via
                                                scripts/generate-ssl-cert.sh)
  - 1× generate_page_fix_prompts.sh           (one-off generated tooling)
  - 4× apps/web/*.json                        (AUDIT_ISSUES, audit_remediation,
                                                lint_comprehensive, storybook-roadmap)

.gitignore enriched (post-audit J2 block) to prevent recommits:
  - veza-backend-api/uploads/                 (audio fixtures → git-lfs or external)
  - config/ssl/*.{pem,key,crt}
  - .playwright-mcp/                          (MCP session debris)
  - CLAUDE_CONTEXT.txt, UI_CONTEXT_SUMMARY.md, *.context.txt  (AI session artefacts)
  - Root PNG prefixes beyond existing rules
  - apps/web/{AUDIT_ISSUES,audit_remediation,lint_comprehensive,storybook-*}.json
  - /generate_page_fix_prompts.sh, /build-archive.log

Next: BFG for history rewrite to compact .git (currently 2.3 GB).

Refs: AUDIT_REPORT.md §9.1, FUNCTIONAL_AUDIT.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 09:56:47 +02:00
..
README.md chore: consolidate CI, E2E, backend and frontend updates 2026-02-17 16:43:21 +01:00
veza.crt BASE: completing the initial repo state 2025-12-03 22:56:50 +01:00

README.md

HAProxy SSL Certificates

Never commit private keys (.key) or certificate files (.pem) to git.

This directory holds SSL certificates for HAProxy HTTPS. The files are gitignored.

Generating Certificates Locally

Self-Signed (Development/Staging)

From the repository root:

cd docker/haproxy/certs
openssl req -x509 -nodes -days 365 -newkey rsa:4096 \
  -keyout veza.key -out veza.crt -subj "/CN=veza.local"
cat veza.crt veza.key > veza.pem

Or use the project script (creates in config/ssl/ — copy to this dir if needed):

./scripts/generate-ssl-cert.sh veza.local
# Then: cp config/ssl/veza.pem config/ssl/key.pem config/ssl/cert.pem docker/haproxy/certs/

Production (Let's Encrypt)

certbot certonly --standalone -d yourdomain.com
cat /etc/letsencrypt/live/yourdomain.com/fullchain.pem \
    /etc/letsencrypt/live/yourdomain.com/privkey.pem > docker/haproxy/certs/veza.pem

Certificate Rotation

If a private key may have been exposed:

  1. Generate new certificate and key (commands above).
  2. Replace veza.pem, veza.key, veza.crt in this directory.
  3. Restart HAProxy.
  4. Document rotation in veza-docs/ if applicable.