Commit Graph

6 Commits

Author SHA1 Message Date
11f1909f68 feat(cd): add continuous deployment on push to master
Some checks failed
CI / ruff (push) Successful in 8s
CI / pytest (push) Successful in 36m19s
CI / architecture (push) Successful in 11s
CI / dependency-scanning (push) Successful in 27s
CI / audit (push) Successful in 9s
CI / docs (push) Failing after 59s
CI / deploy (push) Failing after 3s
Deploy job SSHes to production after ruff/pytest/architecture pass,
running scripts/deploy.sh (stash, pull, docker rebuild, migrate, health check).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 22:42:13 +01:00
874e254c11 fix(ci): use Docker service hostname for PostgreSQL in pytest job
Some checks failed
CI / pytest (push) Failing after 36m48s
CI / dependency-scanning (push) Successful in 27s
CI / audit (push) Successful in 9s
CI / ruff (push) Failing after 7s
CI / architecture (push) Failing after 10s
CI / docs (push) Has been skipped
act_runner executes jobs in Docker containers on the same network as
service containers. Use service name (postgres:5432) instead of
localhost with port mapping.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 09:49:33 +01:00
c58ceb9872 fix(ci): use port 5433 for test PostgreSQL to avoid conflict
Some checks failed
CI / ruff (push) Successful in 8s
CI / pytest (push) Failing after 27s
CI / architecture (push) Failing after 9s
CI / dependency-scanning (push) Successful in 27s
CI / audit (push) Successful in 8s
CI / docs (push) Has been skipped
Production PostgreSQL already uses port 5432 on the host. The CI
test database now maps to port 5433.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 23:38:24 +01:00
e3428cc4aa fix(ci): use uv pip install --system instead of uv sync
Some checks failed
CI / ruff (push) Failing after 14s
CI / pytest (push) Failing after 1s
CI / architecture (push) Successful in 10s
CI / dependency-scanning (push) Successful in 27s
CI / audit (push) Successful in 7s
CI / docs (push) Has been skipped
The act_runner containers don't support uv sync virtual environments
properly. Using --system installs directly into the system Python,
making all tools available on PATH.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 22:59:20 +01:00
7852d09dcc fix(ci): use uv run instead of .venv/bin paths in CI workflow
Some checks failed
CI / ruff (push) Failing after 8s
CI / pytest (push) Failing after 0s
CI / architecture (push) Failing after 8s
CI / dependency-scanning (push) Successful in 26s
CI / audit (push) Failing after 9s
CI / docs (push) Has been skipped
The Gitea Actions runner containers don't expose .venv/bin on the
expected path. Using uv run lets uv resolve the correct environment.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 22:55:06 +01:00
0437af67ec feat(merchant): extract merchant portal as first-class frontend with auth, Tailwind fixes, and Gitea CI
Some checks failed
CI / ruff (push) Has been cancelled
CI / pytest (push) Has been cancelled
CI / architecture (push) Has been cancelled
CI / dependency-scanning (push) Has been cancelled
CI / audit (push) Has been cancelled
CI / docs (push) Has been cancelled
- Extract login/dashboard from billing module into core (matching admin pattern)
- Add merchant auth API with path-isolated cookies (path=/merchants)
- Add merchant base layout with sidebar/header partials and Alpine.js init
- Add frontend detection and login redirect for MERCHANT type
- Wire merchant token in shared api-client.js (get/clear)
- Migrate billing templates to merchant base with dark mode support
- Fix Tailwind: rename shop→storefront in sources and config
- DRY Makefile tailwind targets with TAILWIND_FRONTENDS loop
- Rebuild all Tailwind outputs (production minified)
- Add Gitea Actions CI workflow (ruff, pytest, architecture, docs)
- Add Gitea deployment documentation

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-11 20:25:29 +01:00