nntrivi2001
9c573f1e3c
Decisions, environment quirks and pitfalls learned while working on AgentHub (docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account details are left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
16 lines
1.2 KiB
Markdown
16 lines
1.2 KiB
Markdown
---
|
|
name: agenthub-dev-prod-ports
|
|
description: "4820 = production (systemd, plugin cache build), 4830 = the user's dev server from the checkout in Warp — both on the SAME dashboard.db"
|
|
metadata:
|
|
node_type: memory
|
|
type: project
|
|
originSessionId: e662d0be-af24-4c90-9939-45acfd40e6c3
|
|
modified: 2026-10-05T09:07:39.143Z
|
|
---
|
|
|
|
Port 4820 is production (`agenthub.service`, plugin-cache release build); port 4830 is the user's dev server (`DASHBOARD_PORT=4830 node server/index.js` from the checkout, started by hand in a Warp terminal). As of 2026-10-05 both use the same `~/.claude/agenthub/dashboard.db`.
|
|
|
|
**Why:** a dev server's migrations run on production data (ad6e801 dropping `idx_events_session` froze prod's `/api/workflows`), and every checkout start re-wrote duplicate hooks into `~/.claude/settings.json` (fixed 10-05 in `installHooks`). Hooks reach only the lowest port, so 4830 receives no hook traffic of its own.
|
|
|
|
**How to apply:** when diagnosing lag, check BOTH ports and which code each runs; a hung 4830 is the user's dev instance — tell them to restart it, never kill it yourself. Suggest a separate `DASHBOARD_DATA_DIR` for dev when schema changes are involved. Related: [[agenthub-multi-user-goal]], [[agenthub-flaky-codex-ingest-tests]].
|