[4/4] Wire repository services #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/1-compose-wiring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
backend,egress, andweb-edgenetwork membership127.0.0.1:3406:3000.env.example, Justfile workflows, README setup guidance, and Compose smoke assertionsSize
370 changed lines.
Verification
just configjust lintjust typecheckjust testThe smoke suite passed PostgreSQL/Flyway readiness, application health, exact network membership, port isolation, placeholder PostgreSQL access, and worker TLS egress to both source hosts.
Stack 4 of 4. Depends on and targets
feat/1-web-scaffold; merge the preceding PRs first.Resolves #1
5a21455712toe89ebadec5@ -0,0 +1,68 @@set dotenv-load := truedefault:Rename recipd to help
@ -0,0 +51,4 @@smoke:./scripts/compose-smoke.shgenerate-db-types:If its not needed yet, dont implement it
@ -0,0 +27,4 @@image: flyway/flyway:12-alpinecommand: migrateenvironment:FLYWAY_URL: jdbc:postgresql://postgres:5432/${POSTGRES_DB:-lawnet}No fsllback, fast fai, with :?
e89ebadec5to3e14875004@ -0,0 +46,4 @@config:docker compose configAgain, can you remove all file recipes that aren't needed yet? We'll add them when we need them. Don't add them first and then exit.
@ -0,0 +7,4 @@POSTGRES_DB: ${POSTGRES_DB:-lawnet}POSTGRES_USER: ${POSTGRES_USER:-lawnet}POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-lawnet_dev}healthcheck:We need a separate health check for the Postgres container because it doesn't have one built in. I thought it would include its own health check.
@ -0,0 +27,4 @@image: flyway/flyway:12-alpinecommand: migrateenvironment:FLYWAY_URL: jdbc:postgresql://postgres:5432/${POSTGRES_DB:-lawnet}For this one, fail fast. If the environment variable is not available, use the column‑mark question‑mark syntax.
@ -0,0 +40,4 @@networks:- backenddata-ingest-scheduler:We don't have the implementation for this scheduler. For any service without an implementation, we shouldn't guess the environment variables that follow. Let's trim the compose file as much as possible and remove any unused environment variables.
@ -0,0 +58,4 @@depends_on:flyway:condition: service_completed_successfullyhealthcheck:We don't need a house check for the walkers.
@ -0,0 +85,4 @@depends_on:flyway:condition: service_completed_successfullyhealthcheck:We don't need a health check for the workers here.
Addressed all review comments in commit
8dcc3afb:helpper request.generate-db-types,check-db-types,enqueue-discovery,requeue-dead. Will add when implementations exist.FLYWAY_URL— Changed:-lawnetto:?POSTGRES_DB is requiredfor fail-fast.DATABASE_URL:?. Removed the implementation-guessing vars (DISCOVERY_INTERVAL_HOURS,ARTIFACT_REFRESH_DAYS,WORKER_ID,JOB_LEASE_SECONDS,JOB_MAX_ATTEMPTS,LAWNET_REQUEST_INTERVAL_SECONDS,ELITIGATION_REQUEST_INTERVAL_SECONDS,HTTP_TIMEOUT_SECONDS). Will add back when the scheduler/worker are implemented.@ -0,0 +41,4 @@cd services/web && fnm exec --using=22.22.3 pnpm format:checktypecheck:cd services/data-ingest && uv run pyrightUse ty for checks
@ -0,0 +8,4 @@POSTGRES_USER: ${POSTGRES_USER:-lawnet}POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-lawnet_dev}healthcheck:test:Do we really need a separate health check script for the Postgres container? I expected Postgres would have its own health check.
Second round addressed in commit
6775bcbd:FLYWAY_CONNECT_RETRIES=60). Also removed Flyway'sdepends_onpostgres since Flyway retries on its own.uv run pyrighttouv run ty. Recipe name staystypecheck.pyrightwithtyin dev dependencies.uv lock(removedpyright/nodeenv, addedty).6775bcbdb6toe7080eb24c