10c9e0d854
Complete restructure from patterns/examples/reference to technology-focused directories: • Created technology-specific directories with comprehensive documentation: - /tdarr/ - Transcoding automation with gaming-aware scheduling - /docker/ - Container management with GPU acceleration patterns - /vm-management/ - Virtual machine automation and cloud-init - /networking/ - SSH infrastructure, reverse proxy, and security - /monitoring/ - System health checks and Discord notifications - /databases/ - Database patterns and troubleshooting - /development/ - Programming language patterns (bash, nodejs, python, vuejs) • Enhanced CLAUDE.md with intelligent context loading: - Technology-first loading rules for automatic context provision - Troubleshooting keyword triggers for emergency scenarios - Documentation maintenance protocols with automated reminders - Context window management for optimal documentation updates • Preserved valuable content from .claude/tmp/: - SSH security improvements and server inventory - Tdarr CIFS troubleshooting and Docker iptables solutions - Operational scripts with proper technology classification • Benefits achieved: - Self-contained technology directories with complete context - Automatic loading of relevant documentation based on keywords - Emergency-ready troubleshooting with comprehensive guides - Scalable structure for future technology additions - Eliminated context bloat through targeted loading 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
69 lines
1.6 KiB
Markdown
69 lines
1.6 KiB
Markdown
# Tdarr Server Setup Example
|
|
|
|
## Directory Structure
|
|
```
|
|
~/container-data/tdarr/
|
|
├── docker-compose.yml
|
|
├── stonefish-tdarr-plugins/ # Custom plugins
|
|
├── tdarr/
|
|
│ ├── server/ # Local storage
|
|
│ ├── configs/
|
|
│ └── logs/
|
|
└── temp/ # Local temp if needed
|
|
```
|
|
|
|
## Storage Strategy
|
|
|
|
### Local Storage (Fast Access)
|
|
- **Database**: SQLite requires local filesystem for WAL mode
|
|
- **Configs**: Frequently accessed during startup
|
|
- **Logs**: Regular writes during operation
|
|
|
|
### Network Storage (Capacity)
|
|
- **Backups**: Infrequent access, large files
|
|
- **Media**: Read-only during transcoding
|
|
- **Cache**: Temporary transcoding files
|
|
|
|
## Upgrade Process
|
|
|
|
### Major Version Upgrades
|
|
1. **Backup current state**
|
|
```bash
|
|
docker-compose down
|
|
cp docker-compose.yml docker-compose.yml.backup
|
|
```
|
|
|
|
2. **For clean start** (recommended for major versions):
|
|
```bash
|
|
# Remove old database
|
|
sudo rm -rf ./tdarr/server
|
|
mkdir -p ./tdarr/server
|
|
|
|
# Pull latest image
|
|
docker-compose pull
|
|
|
|
# Start fresh
|
|
docker-compose up -d
|
|
```
|
|
|
|
3. **Monitor initialization**
|
|
```bash
|
|
docker-compose logs -f
|
|
```
|
|
|
|
## Common Issues
|
|
|
|
### Disk Space
|
|
- Monitor local database growth
|
|
- Regular cleanup of old backups
|
|
- Use network storage for large static data
|
|
|
|
### Permissions
|
|
- Container runs as PUID/PGID (usually 0/0)
|
|
- Ensure proper ownership of mounted directories
|
|
- Use `sudo rm -rf` for root-owned container files
|
|
|
|
### Network Filesystem Issues
|
|
- SQLite incompatible with NFS/SMB for database
|
|
- Keep database local, only backups on network
|
|
- Monitor transcoding cache disk usage |