test fixes and doc work
Some checks failed
Deploy to Test Environment / deploy-to-test (push) Failing after 2m50s
Some checks failed
Deploy to Test Environment / deploy-to-test (push) Failing after 2m50s
This commit is contained in:
@@ -2,6 +2,26 @@
|
||||
|
||||
This guide covers deploying Flyer Crawler to a production server.
|
||||
|
||||
## Server Access Model
|
||||
|
||||
**Important**: Claude Code (and AI tools) have **READ-ONLY** access to production/test servers. The deployment workflow is:
|
||||
|
||||
| Actor | Capability |
|
||||
| ------------ | --------------------------------------------------------------- |
|
||||
| Gitea CI/CD | Automated deployments via workflows (has write access) |
|
||||
| User (human) | Manual server access for troubleshooting and emergency fixes |
|
||||
| Claude Code | Provides commands for user to execute; cannot run them directly |
|
||||
|
||||
When troubleshooting deployment issues:
|
||||
|
||||
1. Claude provides **diagnostic commands** for the user to run
|
||||
2. User executes commands and reports output
|
||||
3. Claude analyzes results and provides **fix commands** (1-3 at a time)
|
||||
4. User executes fixes and reports results
|
||||
5. Claude provides **verification commands** to confirm success
|
||||
|
||||
---
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Ubuntu server (22.04 LTS recommended)
|
||||
|
||||
Reference in New Issue
Block a user