Run any Skill in Manus with one click

eweser-docker-debug

Stars48

Forks2

UpdatedApril 29, 2026 at 15:20

Use this skill to debug the EweserDB Docker Compose local development stack. Covers service health checks, log inspection, container exec, volume issues, and common failure patterns for auth-api, sync-server, postgres, and caddy.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

eweser

eweser/eweser-db

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

More from this repository

same repository

eweser-browser-checkpoint

eweser/eweser-db

Use this skill to run a focused browser feedback checkpoint for completed EweserDB UI work. It verifies the specific user-visible behavior from one run or handoff, captures concise evidence, and reports pass/fail without turning into a full exploratory manual test sweep.

2026-05-2648

eweser-coder

eweser/eweser-db

Use this skill to implement a feature in the EweserDB monorepo from a plan file. Also use it when the user invokes $eweser-coder, asks Codex to code an approved EweserDB plan, continue a run from docs/ai/plans, fix a bug, or make repo changes while preserving quality gates. Reads the approved plan at docs/ai/plans/, treats it as the approval boundary, implements all runs, verifies, performs internal QA, fixes issues found inside scope, updates the plan, and ends with self-reflection. Tell Codex which plan file and optionally which run number to start from.

2026-05-2648

eweser-create-pr

eweser/eweser-db

Use this skill to create a GitHub pull request for completed EweserDB work. Summarizes commits since main, writes a clear title and body, and opens the PR. Use after QA has passed.

2026-05-2648

eweser-qa

eweser/eweser-db

Use this skill for standalone re-QA or audit of completed EweserDB work. Also use it when the user invokes $eweser-qa, asks for QA, review, quality assurance, regression checks, test coverage review, or pre-PR verification for EweserDB. Runs relevant verification, reviews code for correctness and security, and verifies Yjs patterns and monorepo consistency. In the canonical Codex Planner -> Coder workflow, Coder owns internal QA; this skill is optional independent review only.

2026-05-2648

eweser-grill-with-docs

eweser/eweser-db

Use this skill in the EweserDB repo when the user wants to stress-test a feature, plan, product decision, or naming choice against EweserDB domain language before implementation. It uses GLOSSARY-MAP.md, package GLOSSARY.md glossaries, INDEX.md navigation, AGENTS.md, and ADRs to challenge fuzzy terms, resolve DDD-style language, update glossary docs, and identify sparse ADR candidates. It ends with self-reflection and skill-improvement suggestions when the session reveals workflow gaps. Planner-style only: do not edit product code.

2026-05-2348

eweser-planner

eweser/eweser-db

Use this skill to create a scoped implementation plan for a feature in the EweserDB monorepo. Also use it when the user invokes $eweser-planner or the legacy personal $eweser-plan name, asks to plan a feature or bug fix, asks for planner/plan-mode behavior, or requests research before implementation for EweserDB. Handles internal research, validation experiments, architecture review, and produces an implementation-ready plan in docs/ai/plans/. Use before starting substantial or ambiguous coding work. Planner stops for user approval and does not implement product code.

2026-05-2348

name	eweser-docker-debug
description	Use this skill to debug the EweserDB Docker Compose local development stack. Covers service health checks, log inspection, container exec, volume issues, and common failure patterns for auth-api, sync-server, postgres, and caddy.

Role: EweserDB Docker Debug

You troubleshoot the EweserDB Docker Compose local development environment.

Services in docker-compose.dev.yml

Service	Default Port	Purpose
`postgres`	5432	PostgreSQL database
`auth-api`	3001	Hono auth server
`sync-server`	38181	Hocuspocus CRDT sync
`caddy`	3000, 443	Reverse proxy
`aggregator`	38190	Aggregator service

Common debug commands

docker compose -f docker-compose.dev.yml up
docker compose -f docker-compose.dev.yml logs -f
docker compose -f docker-compose.dev.yml logs -f auth-api
docker compose -f docker-compose.dev.yml ps
docker compose -f docker-compose.dev.yml exec auth-api sh
docker compose -f docker-compose.dev.yml restart auth-api

Full volume reset destroys local database data:

docker compose -f docker-compose.dev.yml down -v
docker compose -f docker-compose.dev.yml up --build

Common failure patterns

Postgres will not start

Check whether port 5432 is already in use: lsof -i :5432.
Check volume permissions. A volume reset destroys local database data.

Auth API crashes on boot

Missing env vars: compare local env names against packages/auth-server-hono/example.env.
Database not ready yet: check service health and depends_on behavior.

Sync server auth failures

SYNC_AUTH_SECRET must match between auth-api and sync-server.
JWT tokens may be expired. Re-login to refresh them.

Caddy 502 errors

Upstream service may not be running. Check docker compose ps.
Port mismatch. Check docker/Caddyfile against service ports.

Migration not applied

docker compose -f docker-compose.dev.yml exec auth-api npx drizzle-kit migrate

Rebuild after code changes

docker compose -f docker-compose.dev.yml up --build