Releases: RA341/dockman
v2.4.1
v2.4.0
2.4.0 (2025-11-07)
Notes
- Git repos have been removed as the implementation was not useful and more annoying than helpful. Existing installations should not break, but it is still recommended to backup before upgrading.
- Editor UI improvements are still a work in progress, with collapsible and editable panels added.
- A YAML formatter has been added that can format any YAML file by pressing
Alt+L. - ARM64 builds are now available on tags: latest, v2+, and v2.4+.
What's Changed
- fix: header of containers page. by @leafayon in #111
- added collapsable filelist (a61ab1c)
- added yaml formatter (f5ab87a)
- arm64 images (283e52e)
- remove git repo and auto chowning (14e3634)
Bug Fixes
- header of containers page. (5188f8f)
New Contributors
Full Changelog: v2.3.0...v2.4.0
v2.3.0
v2.2.0
This release focuses on quality-of-life improvements and introduces optional configuration support through a optional .dockman.yml config file.
🌐 New Documentation Website
Visit new docs site: https://dockman.radn.dev/
✨ New Features
Configuration Support
- Custom sorting - Configure file sorting behavior via
.dockman.yml - File pinning - Pin frequently used files for quick access
- File renaming - Rename files directly within the interface
Enhanced Editor
- Session persistence - Remember open tabs and cursor positions between sessions
- Improved tab names - Display full file paths for better identification
🐛 Bug Fixes
- Table sorting improvements - Fixed sorting inconsistencies (#71)
- Tab display fixes - Non-compose files no longer show unnecessary tabs (#81)
- TTY stream handling - Resolved terminal stream issues (#76)
- General stability - Various fixes for improved reliability (#85)
Full Changelog: v2.1.2...v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.1.0 (2025-08-13)
This release is mostly UI upgrades with new dedicated pages for managing images, networks, and volumes, plus some improvements to file handling. The volume and network pages are still bare bones while i figure out what to put in there.
Smart compose file detection: Folders containing a single *-compose.yaml file now get promoted to top-level items in the UI for quicker access. Behind the scenes they're still in folders, but the UI displays them as direct stack entries. Folders with multiple compose files or no compose files are treated as regular directories.
Let me know what you think of the new layout!
Other improvements: New keyboard shortcuts have been added throughout the app for better navigation and workflow.
Features
- added configurable cookie expiry limit (a48a382)
- added direct link to stack file from container (5f42658)
- added search and shortcuts for containers and images (e632765)
- image controls (6b37043)
- implemented container controls (dd48570)
- network/volumes/image controls (fa89603)
- new add file dialog (fca7ff2)
- new file item view (d5a146b)
- new shortcuts for file and dashboard (fe1d16e)
v2.0.1
v2.0.0
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: alwaysMigration Steps
-
Stop your current dockman container
docker compose down
-
Update your docker-compose.yml with the new config volume mount (see example above)
-
Remove your old host.yaml file (it's no longer needed)
rm /path/to/your/host.yaml
-
Start dockman with the new configuration
docker compose up -d
-
Reconfigure your multihost settings through the UI instead of the YAML file
Breaking Changes
- 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