Guide for upgrading DisComfy from v1.4.0 to v2.0.0.

DisComfy v2.0.0 introduces a complete architectural overhaul while maintaining 100% backward compatibility. This guide helps you understand the changes and smoothly migrate to the new version.

All changes are backward compatible:

• ✅ Old bot.py entry point still works
• ✅ Existing config.json files compatible
• ✅ All commands function identically
• ✅ Workflows unchanged
• ✅ No database migrations needed

Before (v1.4.0):

discomfy/
├── bot.py           # 3,508 lines
├── image_gen.py     # 2,100+ lines
├── video_gen.py     # Large file
└── config.py

After (v2.0.0):

discomfy/
├── main.py          # New entry point
├── bot/             # 50+ organized modules
│   ├── client.py
│   ├── commands/    # Individual command handlers
│   └── ui/          # Discord UI components
├── core/            # Core functionality
│   ├── comfyui/    # ComfyUI integration
│   ├── generators/ # Generation engines
│   ├── progress/   # Progress tracking
│   └── validators/ # Input validation
├── config/          # Configuration management
└── utils/           # Utility functions

Impact:

• 77% code size reduction (3,508 → 705 lines max)
• 50+ well-organized modules
• Clearer separation of concerns
• Easier testing and maintenance

• ✅ Testing: 85/86 tests passing (99% pass rate)
• ✅ Best Practices: Following discord.py and aiohttp patterns
• ✅ Type Safety: Full Pydantic V2 migration
• ✅ Design Patterns: Strategy, ABC, Factory patterns

• ✅ All commands refactored with new architecture
• ✅ Simplified progress tracking
• ✅ Better error handling
• ✅ Enhanced validation

# Backup your installation
cd discomfy
cp config.json config.json.backup
cp -r workflows workflows.backup
tar -czf discomfy-v1.4.0-backup.tar.gz .

# Pull latest code
git pull origin main

# Or fresh clone
cd ..
git clone https://github.com/jmpijll/discomfy.git discomfy-v2
cd discomfy-v2
cp ../discomfy/config.json .
cp -r ../discomfy/workflows .

# Activate virtual environment
source venv/bin/activate  # Linux/Mac
# or venv\Scripts\activate on Windows

# Update packages
pip install -r requirements.txt --upgrade

# Verify configuration still works
python -c "from config import get_config; print(get_config())"

# Use new entry point (recommended)
python main.py

# Or use old entry point (still works)
python bot.py

In Discord, test:

/status
/generate prompt:test

If everything works, migration is complete!

Old Way (still works):

python bot.py

New Way (recommended):

python main.py

Old Imports (still work):

from image_gen import ImageGenerator
from video_gen import VideoGenerator
from config import get_config

New Imports (recommended):

# ComfyUI Client
from core.comfyui.client import ComfyUIClient

# Generators
from core.generators.image import ImageGenerator
from core.generators.video import VideoGenerator
from core.generators.base import BaseGenerator, GeneratorType

# Configuration (unchanged)
from config import get_config
from config.models import BotConfig

# Validators
from core.validators.image import ImageValidator, PromptParameters

# Utilities
from utils.rate_limit import RateLimiter
from utils.files import save_output_image

# Exceptions
from core.exceptions import (
    ValidationError,
    ComfyUIError,
    GenerationError
)

Old Pattern:

from image_gen import ImageGenerator

generator = ImageGenerator()
await generator.initialize()
images, info = await generator.generate_image(prompt, **params)

New Pattern:

from core.comfyui.client import ComfyUIClient
from core.generators.image import ImageGenerator
from config import get_config

config = get_config()

# Use context manager for automatic cleanup
async with ComfyUIClient(config.comfyui.url) as client:
    generator = ImageGenerator(client, config)
    await generator.initialize()
    # Generate images

Your existing config.json works as-is!

v1.4.0 config.json:

{
  "discord": {
    "token": "YOUR_TOKEN",
    "guild_id": "YOUR_GUILD_ID"
  },
  "comfyui": {
    "url": "http://localhost:8188",
    "timeout": 300
  }
}

v2.0.0 - Same config works:

{
  "discord": {
    "token": "YOUR_TOKEN",
    "guild_id": "YOUR_GUILD_ID"
  },
  "comfyui": {
    "url": "http://localhost:8188",
    "timeout": 300
  }
}

v2.0.0 adds optional new fields:

{
  "discord": {
    "token": "YOUR_TOKEN",
    "guild_id": "YOUR_GUILD_ID",
    "status_message": "🎨 Creating AI art"  // NEW: Custom status
  },
  "comfyui": {
    "url": "http://localhost:8188",
    "timeout": 300,
    "websocket_timeout": 30,     // NEW: WebSocket timeout
    "poll_interval": 2.0          // NEW: Polling interval
  },
  "rate_limit": {                  // NEW: Rate limiting config
    "enabled": true,
    "per_user": 10,
    "global_limit": 100
  },
  "logging": {                     // NEW: Logging config
    "level": "INFO",
    "file": "logs/bot.log"
  }
}

v2.0.0 includes auto-published Docker images!

New registries:

# GitHub Container Registry
docker pull ghcr.io/jmpijll/discomfy:latest
docker pull ghcr.io/jmpijll/discomfy:v2.0.0

# Docker Hub
docker pull jamiehakker/discomfy:latest
docker pull jamiehakker/discomfy:v2.0.0

From v1.4.0:

# Stop old container
docker stop discomfy
docker rm discomfy

# Pull new image
docker pull ghcr.io/jmpijll/discomfy:latest

# Run with same config
docker run -d \
  --name discomfy \
  -v $(pwd)/config.json:/app/config.json:ro \
  -v $(pwd)/outputs:/app/outputs \
  ghcr.io/jmpijll/discomfy:latest

Old docker-compose.yml (v1.4.0):

version: '3.8'
services:
  discomfy:
    build: .
    # ...

New docker-compose.yml (v2.0.0):

version: '3.8'
services:
  discomfy:
    image: ghcr.io/jmpijll/discomfy:latest  # Use pre-built image
    # Or: jamiehakker/discomfy:latest
    # ...same config as before

v2.0.0 includes comprehensive test suite:

# Install test dependencies (included in requirements.txt)
pip install pytest pytest-asyncio pytest-cov

# Run tests
pytest

# Run with coverage
pytest --cov=core --cov=utils --cov=bot

# Verify 85/86 tests pass

After migration, test each command:

/generate prompt:test
/editflux image:<upload> prompt:test
/editqwen image:<upload> prompt:test
/status
/help
/loras

All should work identically to v1.4.0.

If you encounter issues, easy rollback:

# Stop new version
Ctrl+C

# Restore backup
cp config.json.backup config.json
rm -rf workflows
cp -r workflows.backup workflows

# Checkout v1.4.0
git checkout v1.4.0

# Or extract backup
tar -xzf discomfy-v1.4.0-backup.tar.gz

# Start old version
python bot.py

# Stop v2.0.0
docker stop discomfy
docker rm discomfy

# Pull v1.4.0
docker pull ghcr.io/jmpijll/discomfy:v1.4.0

# Run old version
docker run -d \
  --name discomfy \
  -v $(pwd)/config.json:/app/config.json:ro \
  ghcr.io/jmpijll/discomfy:v1.4.0

• Backup current installation
• Pull latest code (git pull)
• Update dependencies (pip install -r requirements.txt --upgrade)
• Test configuration
• Run new version (python main.py)
• Test all commands in Discord
• Verify progress tracking works
• Check logs for errors
• Update documentation links (if applicable)
• Celebrate successful migration! 🎉

Solution:

pip install -r requirements.txt --upgrade

Solution: Old imports still work! No need to change existing code.

Solution:

# Check logs
docker logs discomfy

# Verify image version
docker images | grep discomfy

# Use v1.4.0 if needed
docker pull ghcr.io/jmpijll/discomfy:v1.4.0

Solution: Wait 1-2 minutes for command sync, then restart bot.

• Getting Started - Setup guide for new installations
• Configuration Guide - Complete configuration reference
• API Reference - New API documentation
• Testing Guide - Running and writing tests
• Troubleshooting - Common issues and solutions

After migration:

1. Explore new structure - Browse organized modules
2. Run tests - See comprehensive test suite
3. Read new docs - 24+ documentation files
4. Contribute - Easier to add features now!
5. Stay updated - Check for new releases

• v2.0.0 (November 2025) - Complete architectural overhaul
• v1.4.0 (October 2025) - WebSocket lifecycle fixes
• v1.3.1 (October 2025) - Workflow validation
• v1.3.0 (October 2025) - Multi-image Qwen editing

See Changelog for complete history.

✅ Migration is safe, tested, and backward compatible!

Questions? Check Troubleshooting or create an issue.