- Add comprehensive Tdarr troubleshooting and GPU transcoding documentation - Create /scripts directory for active operational scripts - Archive mapped node example in /examples for reference - Update CLAUDE.md with scripts directory context triggers - Add distributed transcoding patterns and NVIDIA troubleshooting guides - Enhance documentation structure with clear directory usage guidelines 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1.6 KiB
1.6 KiB
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
-
Backup current state
docker-compose down cp docker-compose.yml docker-compose.yml.backup -
For clean start (recommended for major versions):
# Remove old database sudo rm -rf ./tdarr/server mkdir -p ./tdarr/server # Pull latest image docker-compose pull # Start fresh docker-compose up -d -
Monitor initialization
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 -rffor 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