mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-15 23:19:40 +02:00
5a5e24f582
Superseded by the top-level docker-compose.dev.yml (which defines searxng + redis as part of the unified dev stack via `pnpm docker:up`). This per-service file was an artefact from before the unified setup and no script / doc / README still references it. An orphan `mana-searxng-dev` + `mana-search-redis-dev` had been running from this file for ~2 weeks, squatting on the host's port 8080. Every first `pnpm dev:mana:all` after a cold machine start would fail with Bind for 0.0.0.0:8080 failed: port is already allocated because the top-level compose's `mana-searxng` service couldn't take 8080 while the orphan held it. The second invocation silently "worked" — docker saw the freshly-created mana-searxng container and skipped the bind step on the idempotent up, leaving it healthy but only reachable inside the docker network (8080/tcp, no external publish). Cleanup already done out-of-band: docker compose -f services/mana-search/docker-compose.dev.yml down docker compose -f docker-compose.dev.yml up -d --force-recreate searxng Deleting the file so a stale `docker compose -f …/mana-search/dev.yml up` can't resurrect the orphan. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| mana-ai | ||
| mana-analytics | ||
| mana-api-gateway | ||
| mana-auth | ||
| mana-crawler | ||
| mana-credits | ||
| mana-events | ||
| mana-geocoding | ||
| mana-image-gen | ||
| mana-landing-builder | ||
| mana-llm | ||
| mana-mail | ||
| mana-mcp | ||
| mana-media | ||
| mana-notify | ||
| mana-persona-runner | ||
| mana-research | ||
| mana-search | ||
| mana-stt | ||
| mana-subscriptions | ||
| mana-sync | ||
| mana-tts | ||
| mana-user | ||
| mana-video-gen | ||
| mana-voice-bot | ||
| news-ingester | ||