[10] CI and production hardening #10

Closed
opened 2026-06-13 19:00:16 +02:00 by dernbu · 0 comments
Owner

Objective

Make the complete system reproducibly testable and deployable on Forgejo and Docker Compose.

Scope

  • Add Forgejo Actions workflows for Python, TypeScript, database, image, and end-to-end checks.
  • Add complete mocked LawNet and eLitigation fixtures.
  • Validate PostgreSQL 18 Flyway migrations and Kysely type drift.
  • Build all Docker images in CI.
  • Run Playwright smoke tests against the fixture-backed Compose stack.
  • Verify restart behavior, migration ordering, networking, and health checks.
  • Document deployment and the initial progressive discovery run.

Dependencies

Depends on #5, #6, #7, #8, and #9.

Completion criteria

  • CI is green without contacting live sources.
  • A clean Compose deployment reaches a healthy state.
  • Initial discovery progresses while the site remains usable.
  • Only the web service exposes a host port.

Closure

Complete all child issues, or merge a feature-branch pull request that resolves this issue.

Detailed requirements: docs/plans/high-level-plan.md, Phase 10.

## Objective Make the complete system reproducibly testable and deployable on Forgejo and Docker Compose. ## Scope - Add Forgejo Actions workflows for Python, TypeScript, database, image, and end-to-end checks. - Add complete mocked LawNet and eLitigation fixtures. - Validate PostgreSQL 18 Flyway migrations and Kysely type drift. - Build all Docker images in CI. - Run Playwright smoke tests against the fixture-backed Compose stack. - Verify restart behavior, migration ordering, networking, and health checks. - Document deployment and the initial progressive discovery run. ## Dependencies Depends on #5, #6, #7, #8, and #9. ## Completion criteria - CI is green without contacting live sources. - A clean Compose deployment reaches a healthy state. - Initial discovery progresses while the site remains usable. - Only the web service exposes a host port. ## Closure Complete all child issues, or merge a feature-branch pull request that resolves this issue. Detailed requirements: `docs/plans/high-level-plan.md`, Phase 10.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dernbu/lawnet-scraper#10
No description provided.