Document environment access limitations for Claude

- Add section clarifying dev vs production access
- Note that Zabbix, prod IIS, prod DB, prod logs are inaccessible
- Clarify user must relay prod info and deploy changes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
cproudlock
2025-12-11 17:15:27 -05:00
parent eda9cd2208
commit 1bf843fd01

View File

@@ -12,6 +12,24 @@ ShopDB is a Classic ASP/VBScript web application for managing manufacturing shop
- **Server:** IIS on Windows VM (192.168.122.151:8080) - **Server:** IIS on Windows VM (192.168.122.151:8080)
- **Version Control:** Gitea (localhost:3000) - **Version Control:** Gitea (localhost:3000)
## Environment Access
**Claude can access (dev environment):**
- Dev MySQL database via Docker (localhost:3306)
- Dev IIS via Windows VM (192.168.122.151:8080)
- Local files and Gitea
**Claude CANNOT access (production):**
- Production IIS server
- Production IIS logs
- Production MySQL database
- Zabbix server (10.48.130.113)
For production tasks, user must:
- Relay production data/logs to Claude
- Deploy files to production IIS
- Execute database changes on production
## Key Architecture ## Key Architecture
### Database Schema (Phase 2 - Current) ### Database Schema (Phase 2 - Current)