Reference creatortrack port 3070 is prod
name: CreatorTrack :3070 is production, :3060 is dev description: Port mapping for CreatorTrack: :3070 = next start prod (app.creatortrack.ai), :3060 = next dev hot-reload (dev.creatortrack.ai); both share the same lifeos DB type: reference
Port mapping (both share the same lifeos core DB):
| Port | Server | Hostname | Notes |
|---|---|---|---|
| :3070 | next start, NODE_ENV=production |
app.creatortrack.ai (PROD) | Frozen build; requires rebuild+restart to pick up new code; never write test/verification data here |
| :3060 | next dev, NODE_ENV=development |
dev.creatortrack.ai | Hot-reloads from the active branch; safe target for live verification |
Why: an agent verified a new feature end-to-end against :3070 believing it was a dev/staging instance, and it was actually prod, writing test rows (Creatine, Acetaminophen, Vitamin D3) into Justin's real ledger (workspace 67). Because dev and prod share the same DB, the test rows appeared in both.
How to apply: before running any live verification (curl, bot capture tests, DB writes) against a CreatorTrack port, confirm which hostname/environment it maps to. Default to :3060 (dev) for verification. Never write to :3070 without Justin explicitly asking, and never assume a port is safe just because it's numerically different from a known prod port.
[auto-memory session 461b1ad7-a331-4bac-a340-58ef4cd3ee7e, confidence 0.85, mode direct]
Auto-memory addendum 2026-07-04T10:58:51.968409¶
Port-to-environment mapping for CreatorTrack, confirmed by checking process env vars directly (not assumed):
| Port | Server | Hostname | Notes |
|---|---|---|---|
| :3070 | next start, NODE_ENV=production |
app.creatortrack.ai | frozen build until Justin redeploys; NEVER write test data here without asking |
| :3060 | next dev, NODE_ENV=development |
dev.creatortrack.ai | hot-reloads whatever branch is checked out; safe for live verification |
Both servers share the same lifeos core DB, so writes made against either port land in the same real data (workspace 67 etc). There is no environment isolation at the DB layer, only at the app-server layer.
Why: an earlier session verification pass hit :3070 assuming it was dev/staging, and wrote test rows (Creatine, Acetaminophen, Vitamin D3) directly into Justin's real prod workspace. Had to be walked back and cleaned up.
How to apply: before any "let me verify this is live" check or exploratory write against CreatorTrack, confirm which port via ps/env inspection first, and default all interactive/test verification to :3060 (dev). Never write test data to :3070 without explicit permission, since it's Justin's live production data, not a staging copy.
[auto-memory session 461b1ad7-a331-4bac-a340-58ef4cd3ee7e, confidence 0.85]