Trajectory - Inner Map

Slug: self-hosted-dashboard
Source: /Users/nitishchauhan/Downloads/Self-hosted Dashboard.md
Index: Index - Self-hosted Dashboard
Constitution: CONSTITUTION - Publishable Asset Pipeline
Master: 00 - Master Index

1. Prompt spine (human, ordered)

This source is a product-spec blueprint framed for Cursor-on-VPS execution, not a multi-turn debate. The human spine is reconstructed from the document’s address and section order:

P1 - Skip the toy dashboards. You already run things on a VPS and use Cursor. Default “pretty home page” lists are not enough. Want a production-grade, hyper-visual command center that reads real host and container state.
P2 - Give me the exact copy-paste stack. Architecture first, then directory, docker-compose.yml with docker.sock, then the three YAML files that define layout, services, and bookmarks. Executable for Cursor on the VPS terminal, not a conceptual essay.
P3 - Bring it up and prove it. docker compose up -d, open http://YOUR_VPS_IP:3000, confirm live meters and app tiles (Uptime Kuma, Stirling-PDF, Audiobookshelf pattern).
P4 - Make it unavoidable. Wire the dashboard URL into a Custom New Tab / New Tab Override extension so every Ctrl+T surfaces infrastructure.
P5 - Optional polish fork. After the IP version works, ask about reverse proxy (Nginx Proxy Manager class) and a clean domain instead of raw IP.

2. Start state

Ops itch, not research itch. Stack is already accumulating (uptime, PDF tools, media library). Attention problem: services exist but live in separate tabs and mental tabs. Initial curiosity is how do I make the VPS legible at a glance and hard to ignore, using Cursor as the executor rather than hand-typing every path.

Conflict underneath:

Basic dashboard templates feel decorative.
Real need is density + live Docker status + habit surface.
Willing to ship ugly IP:3000 first; domain is a second move.

Posture: director mode. Blueprint in, execute, then habit-lock.

3. Transitions (impulses)

P1 → architecture answer

Frame accepted: Homepage (gethomepage) as modern, minimal, data-dense choice; Docker-native widgets matter more than skin.
Content yank: ASCII “command center” layout (System row + Net Services tiles) makes the target visible before YAML.
Director impulse: stop comparing products; pick one stack and ship the files.

Architecture → compose + three YAMLs

Convinced on mechanism: mounting /var/run/docker.sock is the zero-friction path to live container status.
Config itch satisfied: three-file pattern (settings.yaml, services.yaml, bookmarks.yaml) is a living map of the stack, not one opaque UI form.
Placeholder discipline: YOUR_VPS_IP and container names stay as replace-me tokens for real ports.

YAML → bring-up

Execution heat: docker compose up -d is the only “done” signal that counts.
Visual proof wanted: CPU/RAM/disk widgets and online indicators must appear on first load.
Internal itch remains: Glances/widget wiring may need a real Glances endpoint later; still ship Homepage shell first.

Bring-up → new tab habit

Habit design over more features: the dashboard that you never open is dead config.
Motivation loop claimed: infrastructure on every new tab is the point, not a nice-to-have.
Rejected for now: more apps on the grid before the habit exists.

Habit → reverse proxy question

Partial deferral: domain + TLS is polish after IP works.
Security/legibility itch opens: raw IP is fine for personal ops day one; Nginx Proxy Manager (or equivalent) is the named next hardening step.
End hunt: a dense, Docker-aware Homepage that is both running and unavoidable, with domain left optional.

4. Inner state arc

Stage	State	What was hunted
Start	Stack-scattered, tool-rich, glance-poor	One surface that shows VPS health and app links
Mid	Architecture + compose clarity	Exact files Cursor can place under `~/homepage`
Peak	Three YAML grid as living map	Services and bookmarks as truth of what you run
Habit lock	Ops as default browser state	New tab = command center
End	Shell working; polish deferred	Optional reverse proxy / custom domain only after IP works

Arc in one line: reject decorative dashboards → wire Homepage to Docker → three-file visual config → make it the new tab → domain later.

5. Speech habits visible in this source only

Cursor-as-executor framing: “Tell Cursor to…”, paste structures, run via VPS terminal.
Bypass language: “bypass the basic dashboards,” production-grade, hyper-visual, data-dense.
Step scaffolding with emoji section headers in source (architecture, Docker, visual layout, spin-up, final link); keep the step clarity in Final without chat-fluff.
Concrete stack nouns: Homepage, docker.sock, Glances-style metrics, Uptime Kuma, Stirling-PDF, Audiobookshelf.
Placeholder honesty: YOUR_VPS_IP, container name tokens, “change to your actual ports.”
Habit punchline: Custom New Tab URL / New Tab Override; Ctrl+T as infrastructure flash.
Closing fork as offer: reverse proxy question left open, not forced into the same ship.

6. Writing implications for the Final

Mode: Experiential (Index). Personal infrastructure how-to + habit design, not a research claim.
Open from the scattered-stack / need-a-command-center itch, not from a stock “Wait. Before the map” or binary-is-boring opener.
Keep value blocks close to source: compose, three YAMLs, bring-up, new-tab lock, reverse-proxy as optional next.
Prefer fidelity of the blueprint over clever rewrite; clean junk only.
No em dashes or en dashes in new prose (commas, periods, or spaced hyphen -).
Full name Nitish Chauhan only if branding appears; piece is first-person ops voice for this thread.

Curiosity Rooms

Explorer

Trajectory - Self-hosted Dashboard