Deploying Mylar3
Introduction
Mylar3 is a self-hosted automation tool for managing comic book collections. Similar to what Sonarr is for TV shows or Radarr is for movies, Mylar3 automates the process of tracking, downloading, and organizing comic books. It integrates with Comic Vine for metadata, various download clients, and organizes your collection with proper naming and folder structures.
A continuation of the original Mylar project, Mylar3 is actively maintained with Python 3 support and modern features. It handles both ongoing series and complete runs, automatically downloading new issues as they release while filling in missing back issues from your want list.
Key highlights of Mylar3:
- Automatic Downloads: Monitors for new issues and downloads them automatically
- Comic Vine Integration: Fetches comprehensive metadata from Comic Vine database
- Want List Management: Track missing issues and automatically search for them
- Multiple Download Clients: Supports SABnzbd, NZBGet, and various torrent clients
- Post-Processing: Automatic file organization, renaming, and metadata embedding
- CBZ/CBR Support: Works with standard comic book archive formats
- Reading Integration: Exports to reading applications and libraries
- Series Tracking: Monitor ongoing series with release calendars
- Web Interface: Manage everything through a clean web UI
This guide walks through deploying Mylar3 on Klutch.sh using Docker.
Why Deploy Mylar3 on Klutch.sh
Deploying Mylar3 on Klutch.sh provides several advantages:
Always Monitoring: Your Mylar3 instance runs continuously, never missing new releases from your watched series.
Persistent Library: Your configuration, database, and download history persist across container restarts.
Remote Management: Add new series, check upcoming releases, and manage your collection from anywhere.
Simplified Deployment: Push to GitHub and Klutch.sh handles the infrastructure.
HTTPS by Default: Secure access to your Mylar3 dashboard with automatic SSL certificates.
Prerequisites
Before deploying Mylar3 on Klutch.sh, ensure you have:
- A Klutch.sh account
- A GitHub account with a repository for your configuration
- A Comic Vine API key (free with account)
- Access to Usenet or torrent indexers
- A download client (SABnzbd, NZBGet, or torrent client)
Understanding Mylar3 Architecture
Mylar3 uses several integrated components:
Web Interface: Python-based web application for managing your collection.
Comic Vine API: Primary source for comic metadata, covers, and issue information.
Download Client Integration: Communicates with SABnzbd, NZBGet, or torrent clients to handle downloads.
Indexer Integration: Searches Usenet indexers or torrent trackers for releases.
Post-Processor: Organizes downloaded files with proper naming and folder structure.
SQLite Database: Stores series information, want lists, and history.
Preparing Your Repository
Create a GitHub repository for your deployment.
Repository Structure
mylar3-deploy/├── Dockerfile└── .dockerignoreCreating the Dockerfile
FROM lscr.io/linuxserver/mylar3:latest
# Environment configurationENV PUID=1000ENV PGID=1000ENV TZ=UTC
# Expose web interfaceEXPOSE 8090
# Volumes for data and comicsVOLUME ["/config", "/comics", "/downloads"]Creating the .dockerignore File
.git.github*.mdLICENSE.gitignore.DS_StoreDeploying Mylar3 on Klutch.sh
- Create an account at Comic Vine
- Navigate to the API page
- Copy your API key for later configuration
- Select HTTP as the traffic type
- Set the internal port to 8090
Get Comic Vine API Key
Push Your Repository to GitHub
Initialize and push your repository with the Dockerfile to GitHub.
Create a New Project on Klutch.sh
Navigate to the Klutch.sh dashboard and create a project named “mylar3” or “comics”.
Create a New App
Create a new app and connect your GitHub repository.
Configure HTTP Traffic
Mylar3 serves its web interface over HTTP:
Set Environment Variables
Configure the application:
| Variable | Value |
|---|---|
PUID | 1000 |
PGID | 1000 |
TZ | Your timezone (e.g., America/New_York) |
Attach Persistent Volumes
Configure storage:
| Mount Path | Recommended Size | Purpose |
|---|---|---|
/config | 2 GB | Configuration, database, and cache |
/comics | 100+ GB | Your comic book library |
/downloads | 50 GB | Temporary download location |
Deploy Your Application
Click Deploy to build and start your Mylar3 instance.
Access Mylar3
Visit https://your-app-name.klutch.sh to access the web interface.
Initial Configuration
First-Time Setup
On first access to Mylar3:
- Navigate to Settings (gear icon)
- Complete the configuration wizard
- Set up essential connections
Comic Vine API Configuration
Configure your metadata source:
- Go to Settings > Web Interface
- Enter your Comic Vine API key
- Test the connection
- Configure rate limiting to respect API limits
Download Client Setup
Connect to your download client:
For SABnzbd:
- Go to Settings > Download Settings
- Enable SABnzbd
- Enter SABnzbd URL and API key
- Configure download category
For NZBGet:
- Go to Settings > Download Settings
- Enable NZBGet
- Enter NZBGet URL and credentials
- Configure category mapping
Indexer Configuration
Add your Usenet or torrent indexers:
- Go to Settings > Search Providers
- Add indexer details (URL, API key)
- Test each indexer connection
- Configure priority order
Managing Your Comic Library
Adding Series
Track comic series:
- Go to Comics > Add Series
- Search by name or Comic Vine ID
- Select the correct series from results
- Configure monitoring options:
- All issues
- Future issues only
- Specific issue range
- Set quality preferences
Want List Management
Track missing issues:
- Navigate to Wanted section
- View all missing issues
- Trigger manual searches
- Configure automatic searching
Manual Search
Search for specific issues:
- Find the series in your library
- Locate the specific issue
- Click search icon
- Review and select from results
File Organization
Folder Structure
Configure how Mylar3 organizes files:
- Go to Settings > Import/Export
- Set comic library path
- Configure folder naming template
- Configure file naming template
Naming Templates
Example templates:
Series Folder: {Series Name} ({Year})
Issue File: {Series Name} #{Issue Number} ({Year})
Post-Processing
Automate file handling:
- Enable post-processing in settings
- Configure file operations
- Set up metadata tagging
- Enable cover art embedding
Integration with Reading Apps
Komga Integration
Export to Komga comic server:
- Configure export settings in Mylar3
- Set library path matching Komga
- Enable metadata export
- Trigger library scans
Kavita Integration
Work with Kavita reader:
- Point both applications to same library
- Configure compatible naming
- Enable metadata embedding
- Schedule regular updates
ComicRack/CDisplayEx
For local reading:
- Export with embedded metadata
- Use ComicInfo.xml generation
- Maintain compatible folder structure
Advanced Features
Upcoming Releases
Track future releases:
- Navigate to Upcoming section
- View release calendar
- Configure lookback period
- Set up notifications
Duplicate Handling
Manage multiple versions:
- Configure duplicate detection
- Set quality preferences
- Enable automatic upgrades
- Define keep/replace rules
Mass Editing
Bulk operations:
- Select multiple series
- Apply common settings
- Trigger bulk searches
- Refresh metadata in bulk
Production Best Practices
API Rate Limiting
Respect Comic Vine limits:
- Configure appropriate request intervals
- Use caching for metadata
- Avoid excessive refreshes
Storage Planning
Comic files can be large:
- Plan for 50-500MB per issue for high quality
- Consider series length when estimating
- Monitor storage usage regularly
Backup Strategy
Protect your configuration:
- Backup the
/configdirectory regularly - Export your series list
- Store download history
- Document custom settings
Troubleshooting
Comic Vine API Errors
- Verify API key is valid
- Check rate limiting settings
- Confirm network connectivity
- Review API quota usage
Downloads Not Starting
- Verify download client connection
- Check indexer credentials
- Review category settings
- Check client download queue
Files Not Being Processed
- Verify folder permissions
- Check file naming compatibility
- Review post-processing logs
- Confirm file format support
Missing Series Metadata
- Manual refresh from Comic Vine
- Check series ID mapping
- Verify API connectivity
- Try manual search by Comic Vine ID
Additional Resources
- Mylar3 GitHub Repository
- Mylar3 Wiki
- Comic Vine API
- Klutch.sh Persistent Volumes
- Klutch.sh Deployments
Conclusion
Deploying Mylar3 on Klutch.sh gives you a powerful comic book management system that automatically tracks, downloads, and organizes your collection. The integration with Comic Vine provides rich metadata, while download client integration automates the acquisition process.
Whether you’re keeping up with current releases or building out back issues of classic series, Mylar3 on Klutch.sh provides reliable, always-on management for your comic collection.