Initialize crypto_monitor_user (user edition) from monitor codebase.
Retarget git remote, install path, and deploy docs from crypto_monitor to crypto_monitor_user. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
---
|
||||
description: After each completed code change, commit, push origin/main, and deploy to zk.hyf2.cc
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
# Auto push & deploy
|
||||
|
||||
When a user-facing code change is **finished** (not mid-debug / not "先不要改代码"):
|
||||
|
||||
1. Commit only the relevant files (skip unrelated CRLF-only docs noise).
|
||||
2. `git push origin main` to `https://git.bz121.com/dekun/crypto_monitor_user.git`.
|
||||
3. Deploy to production `zk.hyf2.cc`:`cd /opt/crypto_monitor_user && git pull && bash deploy/pull_and_restart.sh`.
|
||||
4. Confirm PM2 processes are online; briefly report commit hash + deploy status.
|
||||
|
||||
Do **not** wait for the user to say "推送并部署" again unless they cancel this habit.
|
||||
|
||||
SSH: Prefer key auth; if BatchMode fails, use existing Paramiko root login path used in this project.
|
||||
Do not print or put passwords in user-facing replies.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
description: Never trade or close the user's existing option/perp positions during testing
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
# Do not touch existing positions
|
||||
|
||||
When testing option open/close, pending orders, monitors, or any live exchange path on this project:
|
||||
|
||||
- **Never** flatten, reduce, cancel-close, or otherwise close positions the user already holds.
|
||||
- **Never** reuse an existing live position for smoke tests.
|
||||
- If a live trade test is required: open a **new** minimal test position only after explicit approval, then close **only that test position**.
|
||||
- If the only way to verify something needs an existing position: **stop and ask the user first**.
|
||||
- Prefer unit tests / dry paths over live orders when sufficient.
|
||||
Reference in New Issue
Block a user