2.0.0 (2025-07-23)

BREAKING CHANGES

Version 2 introduces a new configuration database for Dockman that will store all application-related data going forward.
Required Action for V2+ Users:

All users upgrading to V2 or later must add the following mount to their Docker Compose configuration:

# docker compose sample

services:
  dockman:
    container_name: dockman
    image: ghcr.io/ra341/dockman:latest
    environment:
      - DOCKMAN_COMPOSE_ROOT=/path/to/stacks
    volumes:
      # these mounts can now be removed
      # - ./config/ssh:/app/config/ssh
      # - ./hosts.yaml:/app/config/hosts.yaml

      # 4️⃣ NEW: Mount config directory for database storage
      # DO NOT store this in dockman compose root

      - /path/to/dockman/config:/config # <--- add this line
    ports:
      - "8866:8866"
    restart: always

Migration Steps

1. Stop your current dockman container

   docker compose down

2. Update your docker-compose.yml with the new config volume mount (see example above)

3. Remove your old host.yaml file (it's no longer needed)

   rm /path/to/your/host.yaml

4. Start dockman with the new configuration

   docker compose up -d

5. Reconfigure your multihost settings through the UI instead of the YAML file

Breaking Changes

⚠️ Important Notes:

• Your existing SSH keys will not be automatically migrated
• You'll need to re-add your remote hosts through the web UI

What's Improved

• Simplified configuration management
• All settings managed through the web interface
• Better persistence with database storage
• No more manual YAML file editing

• Merge pull request #39 from RA341/main (f7f4c0c)

Features

• improved multi-host config and management (3ea713a)
• new version/changelog tracker (05fa5bf)

Bug Fixes

• empty hosts on first login (0bd35c9)
• infinite refresh on git list fail (43c16cf)
• page switch to empty page on host switch (d0a7ca3)
• table and layout issues (a1ba85f)