Files
indee-demo/docker-compose.yml
Dorian 42bd54783a Remove container_name from docker-compose to fix redeploy conflicts
Portainer fails to redeploy when the old containers still exist
with the same hardcoded names. Letting Compose auto-name them
based on the stack/project avoids the conflict.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 12:50:02 +00:00

56 lines
1.3 KiB
YAML

version: '3.8'
services:
# ── Frontend (nginx serving built Vue app) ───────────────────
app:
build:
context: .
dockerfile: Dockerfile
restart: unless-stopped
ports:
- "7777:7777"
depends_on:
seeder:
condition: service_completed_successfully
networks:
- indeedhub-network
labels:
- "com.centurylinklabs.watchtower.enable=true"
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:7777/health"]
interval: 30s
timeout: 10s
retries: 3
start_period: 40s
# ── Nostr Relay (stores comments, reactions, profiles) ───────
relay:
image: scsibug/nostr-rs-relay:latest
restart: unless-stopped
volumes:
- relay-data:/usr/src/app/db
networks:
- indeedhub-network
# ── Seeder (one-shot: seeds test data into relay, then exits) ─
# wait-for-relay.mjs handles readiness polling before seeding.
seeder:
build:
context: .
dockerfile: Dockerfile.seed
depends_on:
- relay
environment:
- RELAY_URL=ws://relay:8080
- ORIGIN=http://localhost:7777
networks:
- indeedhub-network
restart: "no"
networks:
indeedhub-network:
driver: bridge
volumes:
relay-data: