Manor Dev Stack Run Verify
SkillDatabases & dataUse when starting, verifying, debugging, or repairing the local Manor self-hosted dev stack, Docker Compose services, seeded demo login, API/web/worker health, Postgres/Redis/MinIO/sandbox dependencies, or runtime readiness.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Manor Dev Stack Run Verify skill
What this skill tells your AI
The instructions your AI receives, as published by manor-os/manor-ai in .agents/skills/manor-dev-stack-run-verify/SKILL.md and read by ahel’s review.
Use this skill to bring up the local self-hosted Manor stack and prove it is usable.
Default local model
- Compose is the canonical self-hosted path:
docker compose up --build -d. - Default browser entry:
http://localhost:18080. - Seeded local demo account:
demo@manor.local / manor-demo. - Core services: web, API, worker, PostgreSQL + pgvector, Redis, MinIO, Vault, JuiceFS init, sandbox service, and Ollama local embeddings.
Safe startup flow
- Inspect
.envpresence. If missing, copy.env.exampleto.envonly when the user asked to start or initialize local dev. - Check for dirty worktree before destructive cleanup. Never remove volumes or reset data without explicit permission.
- Start or refresh services:
docker compose up --build -d
docker compose ps
- Inspect unhealthy containers with:
docker compose logs --tail=200 <service>
Verification probes
Use available probes in this order:
docker compose ps
curl -fsS http://localhost:18080 >/dev/null
curl -fsS http://localhost:8010/health || curl -fsS http://localhost:18080/health
Then run focused tests for the area being changed:
PYTHONPATH=. .venv/bin/python -m pytest tests/test_health.py tests/test_oss_demo_account.py -q --tb=short -p no:warnings
For frontend changes:
npm --prefix apps/web ci
npm --prefix apps/web run build
Troubleshooting order
- Port conflict: identify owner with
lsof -i :18080or the failing port. - DB/Redis health: inspect compose health status and service logs.
- Migration/init issues: check API logs before editing migrations.
- Sandbox issues: verify sandbox container and network reachability before changing tool runtime code.
- Embedding/RAG issues: inspect
docker compose logs ollama ollama-init --tail=100and confirm themxbai-embed-largemodel is present. - Frontend proxy issues: compare browser URL, API base URL, and compose ports.
Report back
Report service health, URL, login readiness, failed probes, and exact logs/commands used. Name any step skipped because it would be destructive.
Signals
- GitHub stars
- 171
- Forks
- 52
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
manor-dev-stack-run-verify- Source
- github.com/manor-os/manor-ai