Anish Lakhwara
42 lines
1.6 KiB
Markdown
42 lines
1.6 KiB
Markdown
# Box Server Environment
|
|
|
|
You are running on `box`, a NAS server. The user is interacting remotely via mobile phone and cannot run local debugging tools, browser devtools, or inspect terminals directly.
|
|
|
|
## Remote Development Constraints
|
|
|
|
- User has no access to browser devtools or local terminal inspection
|
|
- Be verbose with output - include full error messages and logs
|
|
- Provide curl commands for testing endpoints
|
|
- Explain what's happening at each step since user can't easily inspect
|
|
|
|
## Running Dev Servers
|
|
|
|
When starting development servers or long-running processes:
|
|
|
|
1. **Use the `tmux` skill** - load it with `/skill tmux` for detailed instructions on spawning and managing background processes
|
|
|
|
2. **Port Selection**: Use ports in the range **7000-9000** (firewall is configured for this range)
|
|
|
|
3. **Bind Address**: Always bind to `0.0.0.0`, not `localhost`, so the server is accessible from other devices
|
|
|
|
Example commands:
|
|
- Vite: `npm run dev -- --host 0.0.0.0 --port 7500`
|
|
- Next.js: `npm run dev -- -H 0.0.0.0 -p 7500`
|
|
- Generic: `HOST=0.0.0.0 PORT=7500 npm start`
|
|
|
|
4. **Session Naming**: Name tmux sessions/windows after the project (e.g., `tmux new-window -n "helm-dev" -d`)
|
|
|
|
## Network Access
|
|
|
|
The user can access dev servers at:
|
|
- **Wireguard**: `http://10.0.69.4:<port>` (from any device on the VPN)
|
|
- **LAN**: `http://mossnet.lan:<port>` (from local network)
|
|
|
|
## Debugging
|
|
|
|
Since the user cannot inspect the browser or terminal directly:
|
|
- Always capture and report server logs using `tmux capture-pane`
|
|
- Include full stack traces in responses
|
|
- Suggest curl commands to test API endpoints
|
|
- When something fails, proactively check logs before asking the user
|