alihan/seedbox-lite-torrent
1
0
Fork 0
mirror of https://github.com/hotheadhacker/seedbox-lite.git synced 2025-09-02 00:51:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

chore: Remove outdated documentation files for environment configuration, upload prevention, optimizations, and working state restoration

Browse Source
This commit is contained in:
Salman Qureshi
2025-08-20 20:19:34 +05:30
parent aafe33f0c1
commit 99b34c5853
6 changed files with 4 additions and 465 deletions
Download Patch File Download Diff File Expand all files Collapse all files

104
DEPLOYMENT-READY.md
View File

@@ -1,104 +0,0 @@
# ✅ ENVIRONMENT CONFIGURATION COMPLETE
## 🎯 Mission Accomplished!
Your Seedbox Lite application has been **completely transformed** from hardcoded URLs to a **flexible, environment-driven configuration system**.
## 🔄 What Was Changed
### 🔧 Backend Updates
- ✅ **Environment Variables**: All URLs and configuration now from `.env` files
- ✅ **CORS Configuration**: Dynamic frontend URL support
- ✅ **Server Binding**: Configurable host and port
- ✅ **External APIs**: Subtitle services configurable
- ✅ **Multi-environment Scripts**: dev, prod, docker modes
### 🌐 Frontend Updates
- ✅ **Centralized Config**: All API calls use `config` helper
- ✅ **Environment Support**: Vite integration with env variables
- ✅ **Dynamic URLs**: All components updated to use configurable endpoints
- ✅ **No Hardcoded URLs**: Complete removal of `localhost:3000` references
### 📁 New Files Created
- ✅ `.env` - Development configuration
- ✅ `.env.example` - Configuration template
- ✅ `.env.production` - Production settings
- ✅ `.env.docker` - Docker container config
- ✅ `client/.env` - Frontend variables
- ✅ `client/src/config/environment.js` - Configuration helper
- ✅ `.gitignore` - Protect sensitive config files
## 🚀 Deployment Ready
### Local Development
```bash
# Frontend (from client/)
npm run dev
# Backend (from server-new/)
npm run dev
```
### Different Machine
```bash
# Edit .env with your network settings
SERVER_HOST=192.168.1.100
VITE_API_BASE_URL=http://192.168.1.100:3000
```
### Production Deployment
```bash
# Copy production config
cp .env.production .env
# Edit with your domain
VITE_API_BASE_URL=https://api.yourdomain.com
FRONTEND_URL=https://yourdomain.com
```
### Docker Container
```bash
# Use Docker config
cp .env.docker .env
```
## 🔍 Key Benefits Achieved
1. **🌍 Multi-Machine Deployment**: Easy setup on any network
2. **🐳 Docker Ready**: Container-friendly configuration
3. **🔒 Production Ready**: HTTPS and domain support
4. **⚙️ Developer Friendly**: Flexible local development
5. **🔧 Environment Separation**: Dev, staging, production configs
6. **🛡️ Security**: No hardcoded credentials or URLs in code
## 📋 Current Configuration
### Server Status: ✅ RUNNING
- **URL**: http://localhost:3000
- **Host**: localhost
- **Protocol**: http
- **Frontend**: http://localhost:5173
- **Environment**: development
- **Security**: Download-only mode active
### Configuration Loaded From: `.env`
```
SERVER_PORT=3000
SERVER_HOST=localhost
SERVER_PROTOCOL=http
VITE_API_BASE_URL=http://localhost:3000
FRONTEND_URL=http://localhost:5173
NODE_ENV=development
```
## 🎉 Ready for Any Environment!
Your application is now **completely environment-agnostic** and can be deployed on:
- ✅ Local development machines
- ✅ Remote servers
- ✅ Docker containers
- ✅ Cloud platforms
- ✅ Custom networks
- ✅ Production domains
**No more hardcoded URLs - Your Seedbox Lite is now truly portable!** 🚀

96
NO-UPLOAD-README.md
View File

@@ -1,96 +0,0 @@
# 🔒 DOWNLOAD-ONLY TORRENT CONFIGURATION
## Security Guarantee: ZERO UPLOADS
This application has been configured with **multiple layers of upload prevention** to ensure your system **never uploads or seeds any torrent data**.
## 🛡️ Upload Prevention Layers
### Layer 1: WebTorrent Client Configuration
```javascript
const client = new WebTorrent({
uploadLimit: 0, // Hard limit: 0 bytes/sec upload
dht: false, // No DHT participation
lsd: false, // No local service discovery
pex: false, // No peer exchange
maxConns: 5, // Limited connections
maxWebConns: 3 // Limited web connections
});
```
### Layer 2: Torrent Addition Options
```javascript
client.add(magnetLink, {
upload: false, // Explicitly disable uploads
tracker: false, // No tracker communication
announce: [], // Empty announce list
// ... other download-only options
});
```
### Layer 3: Runtime Upload Blocking
- **Upload Event Monitoring**: Detects and blocks any upload attempts
- **Wire Connection Override**: Prevents data transmission on peer connections
- **Upload Speed Enforcement**: Forces upload speed to 0
- **Large Data Blocking**: Prevents transmission of file chunks
### Layer 4: Network Protocol Restrictions
- **DHT Disabled**: No distributed hash table participation
- **Tracker Disabled**: No communication with torrent trackers
- **Peer Exchange Disabled**: No sharing of peer information
- **Announce Disabled**: No announcing to swarms
## 🔍 Verification
Run the verification script to confirm no uploads:
```bash
node verify-no-uploads.js
```
This script will:
1. ✅ Check all upload prevention configurations
2. 📊 Monitor network activity for 10 seconds
3. 🚨 Alert if any uploads are detected
## 🎯 How It Works
1. **Download Only**: The application downloads torrent pieces for streaming
2. **No Seeding**: Once downloaded, pieces are NOT shared with other peers
3. **Isolated Streaming**: Content is streamed locally without any upload activity
4. **Network Monitoring**: Built-in detection prevents accidental uploads
## 🔧 Configuration Details
The server is configured to:
- Download torrent pieces on-demand for streaming
- Prioritize video file pieces for instant playback
- Buffer minimal data to reduce disk usage
- Block ALL upload attempts at multiple protocol levels
## ⚠️ Important Notes
- **Private Mode**: This is essentially a "private mode" torrent client
- **Download Only**: You are NOT participating in the torrent swarm as a seeder
- **Legal Compliance**: Ensure you have rights to download the content
- **Network Impact**: Zero upload bandwidth usage guaranteed
## 📋 Security Checklist
- [x] Upload limit set to 0 bytes/second
- [x] DHT participation disabled
- [x] Tracker communication disabled
- [x] Peer exchange disabled
- [x] Upload event blocking active
- [x] Wire connection upload prevention
- [x] Network monitoring verification
## 🚀 Usage
1. Start the server: `npm start`
2. Add torrent via web interface
3. Stream content instantly (download-only)
4. Verify no uploads with monitoring script
---
**GUARANTEE**: This configuration ensures your system will NEVER upload or seed torrent data.

122
OPTIMIZATIONS.md
View File

@@ -1,122 +0,0 @@
# SeedBox-Lite Optimization Summary
This document outlines the optimizations made to address API polling issues on low-resource environments (2GB RAM, 1 CPU).
## Problem Diagnosis
The original application had several issues when running on low-resource hardware:
1. **API Timeouts**: Long-running requests (up to 56s) blocked the Node.js event loop
2. **Memory Pressure**: Inefficient streaming caused memory spikes and GC pauses
3. **Connection Pileup**: Frontend kept polling while previous requests were pending
4. **No Request Limits**: The server accepted unlimited concurrent requests
5. **No Timeouts**: Requests could hang indefinitely without resolution
## Key Optimizations
### 1. Server-side Request Management
- **Request Limiter Middleware**: Prevents server overload by limiting concurrent requests
- Implements per-IP request tracking
- Sets appropriate timeouts for all API requests
- Applies different limits based on resource availability
- See: `/server/middleware/requestLimiter.js`
### 2. Optimized Streaming Implementation
- **Chunked Streaming**: Serves content in small chunks (256KB) to prevent memory issues
- Implements proper flow control with stream pause/resume
- Handles range requests efficiently
- Automatically cleans up resources on client disconnect
- See: `/server/handlers/optimizedStreamingHandler.js`
### 3. Resilient Client-side Fetching
- **Enhanced API Client**: Prevents API pileup with smart request handling
- Implements timeouts, retries, and exponential backoff
- Deduplicates identical pending requests
- Features circuit breaker to prevent request floods
- See: `/client/src/utils/apiClient.js`
### 4. Adaptive Polling
- **Smart Polling Hook**: React hook that adapts to server conditions
- Dynamically adjusts polling interval based on response times
- Backs off exponentially when errors occur
- Implements circuit breaking on consecutive failures
- See: `/client/src/hooks/useSmartPolling.js`
### 5. Resource-Aware Configuration
- **Environmental Detection**: Server auto-configures based on available resources
- Adjusts connection limits for low-resource environments
- Sets appropriate timeouts based on system capabilities
- See: `/server/index-optimized.js`
## Implementation Guide
To implement these optimizations:
1. Replace the existing stream handler with the optimized one
```javascript
// In server/index.js
const streamHandler = require('./handlers/optimizedStreamingHandler');
app.get('/api/torrents/:identifier/files/:fileIdx/stream', streamHandler);
```
2. Add the request limiter middleware
```javascript
// In server/index.js
const createRequestLimiter = require('./middleware/requestLimiter');
app.use(createRequestLimiter({
maxConcurrentRequests: 15,
requestTimeout: 30000,
logLevel: 1
}));
```
3. Use the enhanced API client in frontend components
```javascript
// In your React components
import { api } from '../utils/apiClient';
// Use it for API calls
api.get('/api/torrents')
.then(data => console.log(data))
.catch(err => console.error(err));
```
4. Implement the smart polling hook for data fetching
```javascript
// In your React components
import useSmartPolling from '../hooks/useSmartPolling';
function TorrentList() {
const fetchTorrents = async (signal) => {
const response = await fetch('/api/torrents', { signal });
return response.json();
};
const { data, error, isLoading, refresh } = useSmartPolling(fetchTorrents);
// Use data, handle loading/error states
}
```
5. For full optimization, consider using the completely optimized server:
```bash
# Run the optimized version
node server/index-optimized.js
```
## Results
These optimizations should significantly improve your application's performance on low-resource environments:
- **Reduced Memory Usage**: Smaller chunks and better resource cleanup
- **More Responsive API**: Limited concurrent requests prevents overload
- **Fewer Pending Requests**: Smart polling prevents request pileup
- **Graceful Degradation**: System adapts to resource constraints
- **Improved Stability**: Proper error handling and recovery mechanisms
If you encounter any issues, refer to the detailed comments in each file for troubleshooting guidance.

4
README.md
View File

@@ -9,6 +9,10 @@
**A modern, lightweight torrent streaming application with instant playback** **A modern, lightweight torrent streaming application with instant playback**
<img src="https://raw.githubusercontent.com/hotheadhacker/seedbox-lite/refs/heads/main/screenshots/details-screen.png" alt="SeedBox Lite Screenshot" width="80%"/>
[View all screenshots](https://github.com/hotheadhacker/seedbox-lite/tree/main/screenshots)
[Features](#-features) • [Screenshots](#-screenshots) • [Quick Start](#-quick-start) • [Installation](#-installation) • [Documentation](#-documentation) [Features](#-features) • [Screenshots](#-screenshots) • [Quick Start](#-quick-start) • [Installation](#-installation) • [Documentation](#-documentation)
</div> </div>

67
SECURITY-VERIFICATION.md
View File

@@ -1,67 +0,0 @@
# 🔒 SECURITY CONFIRMED: ZERO UPLOAD CONFIGURATION
## ✅ VERIFICATION COMPLETE
Your torrent application has been successfully configured with **ABSOLUTE ZERO UPLOAD PREVENTION**. Multiple security layers have been implemented and verified.
## 🛡️ Security Layers Confirmed Active
### ✅ Layer 1: WebTorrent Client Configuration
- **Upload Limit**: Hard-capped at 0 bytes/second
- **DHT Disabled**: No distributed hash table participation
- **Local Service Discovery Disabled**: No peer discovery on local network
- **Peer Exchange Disabled**: No sharing of peer information
### ✅ Layer 2: Torrent Addition Restrictions
- **Upload Flag**: Explicitly set to `false`
- **Tracker Communication**: Completely disabled
- **Announce List**: Empty (no tracker announcements)
### ✅ Layer 3: Runtime Upload Blocking
- **Upload Event Monitoring**: Active detection and blocking
- **Wire Connection Override**: Prevents data transmission
- **Large Data Blocking**: Blocks file chunk uploads
### ✅ Layer 4: API Security
- **Upload Speed**: Always reported as 0
- **Upload Count**: Always reported as 0
- **Seed Ratio**: Always reported as 0
- **Seeding Status**: Always reported as false
## 🎯 What This Means
1. **Zero Network Uploads**: Your system will NOT upload any torrent data
2. **Download Only**: You only receive data, never send it
3. **Private Mode**: You're not participating in torrent swarms as a seeder
4. **Bandwidth Safe**: No upload bandwidth will be consumed
## 📊 Network Monitoring Results
The verification script confirmed:
- ✅ All 8 upload prevention configurations are active
- ✅ No upload activity detected during monitoring
- ✅ System is configured for download-only operation
## 🚨 Important Notes
- **Legal Compliance**: Ensure you have rights to download content
- **No Seeding**: This configuration prevents contributing back to swarms
- **Detection Proof**: Upload blocking is verified and active
- **Security Guaranteed**: Multiple redundant layers prevent any uploads
## 🔧 Files Modified
1. `server-new/index.js` - Ultra-strict WebTorrent configuration
2. `verify-no-uploads.js` - Network monitoring verification
3. `NO-UPLOAD-README.md` - Security documentation
## 📋 Usage Verification
To verify the configuration anytime:
```bash
node verify-no-uploads.js
```
---
**SECURITY GUARANTEE**: This application will NEVER upload or seed torrent data. Your network upload activity from torrents is ZERO.

76
WORKING-STATE-RESTORED.md
View File

@@ -1,76 +0,0 @@
# ✅ WORKING STATE RESTORED - Universal Torrent Resolution System
## 🔄 What Was Fixed
**Problem**: Torrents were getting added but couldn't be viewed - "not found" errors when navigating to torrent details.
**Root Cause**: The clean version only kept torrents in memory and the GET endpoint couldn't reload missing torrents.
**Solution**: Restored the **Universal Torrent Resolution System** which can:
- ✅ Add torrents successfully
- ✅ View torrents even after server memory clears
- ✅ Automatically reload torrents on-demand
- ✅ Multiple fallback strategies for finding torrents
## 🚀 Current System Status
### Backend: Universal Torrent Resolution System
- **Server**: `http://localhost:3000`
- **File**: `index-universal.js` (deployed as `index.js`)
- **Features**:
- 6-strategy torrent resolution
- Automatic on-demand loading
- Zero upload security maintained
- Comprehensive torrent tracking
### Frontend: Working Integration
- **Frontend**: `http://localhost:5173`
- **Navigation**: Correctly uses `data.infoHash` for routing
- **API Integration**: Properly sends `{ torrentId: magnetLink }` format
- **Environment**: Configured for correct ports
## 🎯 Universal Resolution Strategies
1. **Direct Hash Match**: Check if torrent exists in memory
2. **ID Lookup**: Search by stored torrent IDs
3. **Name Lookup**: Find by torrent name
4. **Hash Registry**: Check comprehensive hash registry
5. **Client Search**: Deep search in WebTorrent client
6. **Direct Loading**: Load fresh if identifier looks like magnet/hash
## 🔧 How It Works Now
```
Add Torrent → Universal Resolver Stores → View Anytime → Auto-Reload if Missing
```
### Add Flow:
1. User submits magnet link
2. Universal system loads torrent
3. Stores in multiple tracking systems
4. Returns `infoHash` for navigation
5. Frontend navigates to `/torrent/{infoHash}`
### View Flow:
1. User visits `/torrent/{infoHash}`
2. Universal resolver tries 6 strategies
3. If not found in memory, auto-reloads
4. Returns torrent details or helpful error
## 🛡️ Security Maintained
- **Zero Upload Policy**: Complete upload blocking
- **No Seeding**: All upload attempts terminated
- **Download Only**: Strict download-only mode
- **Runtime Monitoring**: Continuous security enforcement
## 🎉 Ready to Test!
Your system is now fully operational:
1. **Open**: `http://localhost:5173`
2. **Add any magnet link**
3. **Navigate to torrent details** - should work perfectly!
4. **Restart server and try again** - torrents will auto-reload!
The Universal Torrent Resolution System guarantees that **torrents can always be viewed** once added, solving the core issue you were experiencing! 🚀