keith/MeshVault
1
0 Fork 0
Code Issues 44 Pull Requests Actions Packages Projects Releases Wiki Activity

Docker Compose stack: nginx, PHP-FPM, PostgreSQL, Node #6

New Issue
Closed
opened 2026-10-10 22:18:17 +00:00 by keith · 1 comment
keith commented 2026-10-10 22:18:17 +00:00
Owner
Copy link
Copy source

Provide the runnable local stack described in the technology section of the spec.

Scope

  • docker-compose.yml with services: web (nginx), app (PHP-FPM), db (PostgreSQL), assets (Node build)
  • Named volume for PostgreSQL data
  • Bind mounts for the managed library directory and the application source in dev
  • Health checks for db; app waits for a healthy database

Acceptance criteria

  • docker compose up yields a reachable PHP page served by nginx
  • PostgreSQL data survives docker compose down and restart
  • Library directory is mounted read-write and visible to the app container

Blocked by: #4

Provide the runnable local stack described in the technology section of the spec. ## Scope - `docker-compose.yml` with services: `web` (nginx), `app` (PHP-FPM), `db` (PostgreSQL), `assets` (Node build) - Named volume for PostgreSQL data - Bind mounts for the managed library directory and the application source in dev - Health checks for `db`; `app` waits for a healthy database ## Acceptance criteria - [ ] `docker compose up` yields a reachable PHP page served by nginx - [ ] PostgreSQL data survives `docker compose down` and restart - [ ] Library directory is mounted read-write and visible to the app container --- Blocked by: #4
keith added this to the M1 - Docker & Dev Environment milestone 2026-10-10 22:18:17 +00:00
keith added the type:chorearea:infrapriority:high labels 2026-10-10 22:18:17 +00:00
keith commented 2026-10-12 18:54:33 +00:00
Author
Owner
Copy link
Copy source

Acceptance reconciliation at c1ef2ee: Compose services, PG health gate/volume and writable library bind are implemented. Historical M1 runtime checks recorded HTTP reachability, writes as www-data and database marker survival across down/up (M1 task3/task5 reports). These are historical Linux checks, not a fresh Docker replay. Closing on that evidence; not a production-readiness claim.

Acceptance reconciliation at c1ef2ee: Compose services, PG health gate/volume and writable library bind are implemented. Historical M1 runtime checks recorded HTTP reachability, writes as www-data and database marker survival across down/up (M1 task3/task5 reports). These are historical Linux checks, not a fresh Docker replay. Closing on that evidence; not a production-readiness claim.
keith closed this issue 2026-10-12 18:54:34 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:backend
PHP application logic
 area:db
PostgreSQL schema and migrations
 area:frontend
PHP views, Tailwind, browser JS
 area:indexer
Scanning, hashing, import pipeline
 area:infra
Docker, CI, deployment
 priority:high
Blocking or critical path
 priority:low
Nice to have
 priority:medium
Normal priority
 type:bug
Defect
 type:chore
Tooling, scaffolding, maintenance
 type:decision
Architecture decision record
 type:docs
Documentation
 type:feature
New user-facing capability
No labels area:infra priority:high type:chore
Milestone
No items
No Milestone M1 - Docker & Dev Environment
Projects
Clear projects
No projects
Assignees
Clear assignees
keith (Keith Solomon)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: keith/MeshVault#6