docs: Add 1-minute simplified price feed to reduce TradingView alert queue pressure
- Create moneyline_1min_price_feed.pinescript (70% smaller payload) - Remove ATR/ADX/RSI/VOL/POS from 1-minute alerts (not used for decisions) - Keep only price + symbol + timeframe for market data cache - Document rationale in docs/1MIN_SIMPLIFIED_FEED.md - Fix: 5-minute trading signals being dropped due to 1-minute flood (60/hour) - Impact: Preserve priority for actual trading signals
This commit is contained in:
mindesbunister
314
docs/deployments/README.md
Normal file
314
docs/deployments/README.md
Normal file
@@ -0,0 +1,314 @@
|
||||
# Deployment Status & Verification
|
||||
|
||||
**Verification reports for major feature deployments.**
|
||||
|
||||
This directory contains *_COMPLETE.md and DEPLOYMENT_*.md status files documenting deployment verification for significant system changes.
|
||||
|
||||
---
|
||||
|
||||
## ✅ Recent Deployments
|
||||
|
||||
### **December 2025**
|
||||
- `DEPLOYMENT_SUCCESS_DEC3_2025.md` - **Bug fixes deployment**
|
||||
- Bug #1: Revenge system external closure integration
|
||||
- Bug #5: Smart Validation Queue bypass in execute endpoint
|
||||
- 2 critical fixes deployed and verified
|
||||
- **Status:** ✅ VERIFIED (Dec 3, 09:02 UTC)
|
||||
|
||||
### **November 2025**
|
||||
- `V9_IMPLEMENTATION_COMPLETE.md` - **v9 Money Line indicator**
|
||||
- MA Gap analysis (±5 to +15 quality points)
|
||||
- Momentum-Based SHORT Filter (ADX ≥23, Position-based entry)
|
||||
- Quality thresholds: LONG ≥90, SHORT ≥80
|
||||
- **Status:** ✅ PRODUCTION (Nov 26, 2025)
|
||||
|
||||
- `PHASE_7.3_ADAPTIVE_TRAILING_DEPLOYED.md` - **Adaptive trailing stop**
|
||||
- Real-time 1-minute ADX monitoring
|
||||
- Dynamic multipliers: ADX acceleration/deceleration
|
||||
- Combined max: 3.16× for strong trending moves
|
||||
- **Status:** ✅ DEPLOYED (Nov 27, 2025)
|
||||
|
||||
- `ONE_YEAR_RETENTION_DEPLOYMENT.md` - **Data retention policy**
|
||||
- Database: 1 year retention for Trade/PriceUpdate tables
|
||||
- BlockedSignal: 90 days retention
|
||||
- Automated cleanup job
|
||||
- **Status:** ✅ ACTIVE
|
||||
|
||||
- `RUNNER_SYSTEM_FIX_COMPLETE.md` - **Runner stop loss protection**
|
||||
- Fixed: No SL protection between TP1 and TP2
|
||||
- Added: Explicit runner SL check in monitoring loop
|
||||
- ADX-based runner SL positioning
|
||||
- **Status:** ✅ VERIFIED (Nov 15, 2025)
|
||||
|
||||
- `REENTRY_SYSTEM_COMPLETE.md` - **Manual trade validation**
|
||||
- Fresh TradingView data validation (<5min old)
|
||||
- Recent performance modifiers (±20 points)
|
||||
- Minimum score 55 (vs 60 for new signals)
|
||||
- **Status:** ✅ OPERATIONAL
|
||||
|
||||
- `MA_CROSSOVER_DETECTION_COMPLETE.md` - **MA crossover tracking**
|
||||
- n8n Parse Signal Enhanced detects "crossing" keyword
|
||||
- Flags: isMACrossover, isDeathCross, isGoldenCross
|
||||
- Purpose: Data collection for ADX weak→strong validation
|
||||
- **Status:** ✅ IMPLEMENTED (Nov 27, 2025)
|
||||
|
||||
- `CLUSTER_STOP_BUTTON_FIX_COMPLETE.md` - **Cluster control UI**
|
||||
- Database-first status detection (SSH supplementary)
|
||||
- Stop button properly shown when cluster active
|
||||
- Conditional rendering based on cluster status
|
||||
- **Status:** ✅ DEPLOYED (Nov 30, 2025)
|
||||
|
||||
- `SMART_ENTRY_DEPLOYMENT_STATUS.md` - **Smart Entry Validation Queue**
|
||||
- Block & Watch system for quality 50-89 signals
|
||||
- ±0.3% confirmation thresholds (optimized from backtest)
|
||||
- 30-second monitoring with 10-minute expiry
|
||||
- **Status:** ✅ ACTIVE (Nov 30, 2025)
|
||||
|
||||
- `SMART_ENTRY_TIMING_STATUS.md` - **Smart Entry pullback detection**
|
||||
- Waits for 0.5-2% pullback before entry
|
||||
- Adaptive based on ATR and market conditions
|
||||
- Improves entry prices on quality 85+ signals
|
||||
- **Status:** ✅ ENABLED
|
||||
|
||||
- `TP1_FIX_DEPLOYMENT_SUMMARY.md` - **TP1 detection accuracy**
|
||||
- Fixed: TP1 detection when on-chain orders fill fast
|
||||
- Percentage-based exit reason inference (0.3-1.2% = TP1)
|
||||
- Database records now accurate
|
||||
- **Status:** ✅ VERIFIED (Nov 19, 2025)
|
||||
|
||||
- `PHASE_4_VERIFICATION_COMPLETE.md` - **Historical verification**
|
||||
- Phase 4 position scaling optimizations
|
||||
- TP2-as-runner system validation
|
||||
- 40% runner with ATR trailing stop
|
||||
- **Status:** ✅ COMPLETE
|
||||
|
||||
---
|
||||
|
||||
## 📋 Deployment Checklist Template
|
||||
|
||||
**For Every Major Deployment:**
|
||||
|
||||
### **1. Pre-Deployment**
|
||||
- [ ] Code changes committed and pushed
|
||||
- [ ] Unit tests pass (if applicable)
|
||||
- [ ] Integration tests pass
|
||||
- [ ] Documentation updated (copilot-instructions.md)
|
||||
- [ ] Deployment doc created in this directory
|
||||
|
||||
### **2. Build & Deploy**
|
||||
```bash
|
||||
# Build Docker image
|
||||
cd /home/icke/traderv4
|
||||
docker compose build trading-bot
|
||||
|
||||
# Restart container
|
||||
docker compose up -d --force-recreate trading-bot
|
||||
|
||||
# Verify container running
|
||||
docker ps | grep trading-bot
|
||||
```
|
||||
|
||||
### **3. Verification**
|
||||
```bash
|
||||
# 1. Check container start time > commit time
|
||||
echo "=== Container Start Time ===" && \
|
||||
docker inspect trading-bot-v4 --format='{{.State.StartedAt}}'
|
||||
|
||||
echo -e "\n=== Recent Commits ===" && \
|
||||
git log --oneline --since="YYYY-MM-DD HH:MM" --format='%h %ai %s'
|
||||
|
||||
# 2. Verify logs show expected behavior
|
||||
docker logs -f trading-bot-v4 | grep -E "expected_log_pattern"
|
||||
|
||||
# 3. Test API endpoints
|
||||
curl http://localhost:3001/api/endpoint/path
|
||||
|
||||
# 4. Database verification (if schema changes)
|
||||
docker exec trading-bot-postgres psql -U postgres -d trading_bot_v4 -c "\\dt"
|
||||
```
|
||||
|
||||
### **4. Post-Deployment**
|
||||
- [ ] Container start time > all commit timestamps ✅
|
||||
- [ ] Expected log messages appear ✅
|
||||
- [ ] API endpoints respond correctly ✅
|
||||
- [ ] Database schema correct (if applicable) ✅
|
||||
- [ ] Test trade executed successfully (if trading logic changed) ✅
|
||||
- [ ] User notified of deployment ✅
|
||||
|
||||
### **5. Documentation**
|
||||
- [ ] Deployment doc updated with verification results
|
||||
- [ ] Common Pitfalls added (if bug fix)
|
||||
- [ ] Roadmap updated (if completing phase)
|
||||
- [ ] Git commit for deployment verification
|
||||
|
||||
---
|
||||
|
||||
## 🚨 Critical Deployment Rules
|
||||
|
||||
**NEVER declare "deployed" or "working" without:**
|
||||
1. ✅ Verifying container start time > commit timestamp
|
||||
2. ✅ Observing expected logs in production
|
||||
3. ✅ Testing API endpoint or feature behavior
|
||||
4. ✅ SQL query confirming database state (if applicable)
|
||||
5. ✅ Test trade validation (if Position Manager changes)
|
||||
|
||||
**Why This Matters:**
|
||||
- This is a **real money trading system**
|
||||
- Premature "working" declarations cause financial losses
|
||||
- Container restart required for code changes to take effect
|
||||
- Code committed ≠ Code deployed ≠ Code verified
|
||||
|
||||
---
|
||||
|
||||
## 📝 Creating Deployment Docs
|
||||
|
||||
**Naming Convention:**
|
||||
- `[FEATURE]_COMPLETE.md` - Major feature fully implemented
|
||||
- `DEPLOYMENT_SUCCESS_[DATE].md` - Multiple fixes deployed together
|
||||
- `PHASE_[N]_VERIFICATION_COMPLETE.md` - Roadmap phase completion
|
||||
|
||||
**Required Sections:**
|
||||
```markdown
|
||||
# [Feature Name] - DEPLOYED ([Date])
|
||||
|
||||
**Purpose:** [What this deployment does]
|
||||
|
||||
**Status:** ✅ VERIFIED | ⏳ PENDING | ❌ FAILED
|
||||
|
||||
---
|
||||
|
||||
## Changes Deployed
|
||||
|
||||
### **Files Modified**
|
||||
- `path/to/file1.ts` - [Description]
|
||||
- `path/to/file2.ts` - [Description]
|
||||
|
||||
### **Key Improvements**
|
||||
1. [Change 1]
|
||||
2. [Change 2]
|
||||
|
||||
---
|
||||
|
||||
## Deployment Process
|
||||
|
||||
**Build Time:** [Time]
|
||||
**Container Restart:** [Time]
|
||||
**Git Commit:** [Hash] - [Message]
|
||||
|
||||
### **Verification Steps**
|
||||
```bash
|
||||
# Commands used to verify deployment
|
||||
```
|
||||
|
||||
### **Verification Results**
|
||||
- ✅ Container start time: [Time] > Commit time: [Time]
|
||||
- ✅ Expected logs observed: "[Log message]"
|
||||
- ✅ API test successful: [Response]
|
||||
- ✅ Database state correct: [Query results]
|
||||
|
||||
---
|
||||
|
||||
## Expected Behavior
|
||||
|
||||
**Before Deployment:**
|
||||
- [Old behavior description]
|
||||
|
||||
**After Deployment:**
|
||||
- [New behavior description]
|
||||
|
||||
---
|
||||
|
||||
## Monitoring
|
||||
|
||||
**What to Watch:**
|
||||
- [Log patterns to monitor]
|
||||
- [Database queries to check]
|
||||
- [API endpoints to test]
|
||||
|
||||
**Success Indicators:**
|
||||
- [How to know it's working correctly]
|
||||
|
||||
**Failure Indicators:**
|
||||
- [How to detect problems]
|
||||
|
||||
---
|
||||
|
||||
## Rollback Procedure
|
||||
|
||||
**If Problems Occur:**
|
||||
```bash
|
||||
# Revert to previous container
|
||||
docker tag traderv4-trading-bot:backup traderv4-trading-bot:latest
|
||||
docker compose up -d --force-recreate trading-bot
|
||||
|
||||
# Or git revert
|
||||
git revert [commit_hash]
|
||||
git push
|
||||
# Then rebuild/restart
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Impact
|
||||
|
||||
**Expected:**
|
||||
- [Benefit 1]
|
||||
- [Benefit 2]
|
||||
|
||||
**Actual:** (Update after 24-48 hours)
|
||||
- [Measured impact]
|
||||
|
||||
---
|
||||
|
||||
## Lessons Learned
|
||||
|
||||
1. [Key insight #1]
|
||||
2. [Key insight #2]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔍 Finding Deployment Info
|
||||
|
||||
**By Date:**
|
||||
- Most recent → Check filename dates (YYYY-MM-DD or Month YYYY)
|
||||
- Historical → Older files in this directory
|
||||
|
||||
**By Feature:**
|
||||
- v9 indicator → `V9_IMPLEMENTATION_COMPLETE.md`
|
||||
- Trailing stops → `PHASE_7.3_ADAPTIVE_TRAILING_DEPLOYED.md`
|
||||
- Runner system → `RUNNER_SYSTEM_FIX_COMPLETE.md`
|
||||
- Smart Entry → `SMART_ENTRY_*_STATUS.md`
|
||||
- Cluster UI → `CLUSTER_STOP_BUTTON_FIX_COMPLETE.md`
|
||||
|
||||
**By Status:**
|
||||
- ✅ VERIFIED → Deployment confirmed working
|
||||
- ⏳ PENDING → Awaiting verification
|
||||
- 🔄 IN PROGRESS → Deployment ongoing
|
||||
|
||||
---
|
||||
|
||||
## 📊 Deployment Metrics
|
||||
|
||||
**Success Rate:**
|
||||
- Track deployments requiring rollback
|
||||
- Track verification time (commit → confirmed working)
|
||||
- Track time to detect issues
|
||||
|
||||
**Typical Timeline:**
|
||||
- Code change → Commit: 5-30 minutes
|
||||
- Build Docker image: 60-90 seconds
|
||||
- Container restart: 5-10 seconds
|
||||
- Verification: 1-5 minutes
|
||||
- **Total:** 10-45 minutes from code to verified
|
||||
|
||||
**Best Practices:**
|
||||
- Always use `--force-recreate` flag for container restart
|
||||
- Wait 10 seconds after restart before testing
|
||||
- Test in order: Logs → API → Database → Feature
|
||||
- Document verification steps in deployment doc
|
||||
- Update roadmaps after phase completions
|
||||
|
||||
---
|
||||
|
||||
See `../README.md` for overall documentation structure.
|
||||
Reference in New Issue
Block a user