Files
proxmox/.cursor/rules/operator-context-lan-proxmox.mdc
defiQUG b3a8fe4496
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
chore: sync all changes to Gitea
- Config, docs, scripts, and backup manifests
- Submodule refs unchanged (m = modified content in submodules)

Made-with: Cursor
2026-03-02 11:37:34 -08:00

11 lines
882 B
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
description: This machine has LAN and Proxmox access; operator scripts can be run from here
alwaysApply: true
---
# Operator context — LAN and Proxmox
**Remember:** This machine **is** LAN/operator — it has LAN and Proxmox access to 192.168.11.x. Operator scripts **can and should** be run from here when the user asks to run operator tasks.
When suggesting or running operator/LAN tasks (e.g. `run-all-operator-tasks-from-lan.sh`, contract verification, NPMplus backup, nginx/VMID 5000, token-aggregation DB, E2E checks), assume this host can reach Proxmox hosts (192.168.11.1012), Chain 138 RPC (192.168.11.211:8545), NPMplus, and Blockscout. Do not treat operator tasks as "unrunnable from this environment" unless a specific credential or network constraint is missing. Only credentials in `.env` (e.g. `NPM_PASSWORD`, `PRIVATE_KEY`) are required to execute them.