Title: Feature request: allow container ordering across folder boundaries (for autostart sequencing)
Body:
Currently, drag-and-drop reordering and the resulting autostart sync only work within a single folder. Containers are grouped into folders primarily for organizational/visual purposes, but this means the actual Docker autostart order ends up tied to folder membership — you can reorder containers inside a folder, but you can't interleave containers from different folders into a single custom startup sequence.
Use case:
I organize containers into folders by function (Network, Database, Security, etc.), but I need a specific startup order that cuts across those folders — e.g., a DNS container from "Network", followed by one from "Security", followed by a database container from "Database". Right now this isn't possible without merging those containers into one folder, which breaks the organizational structure I want to keep for the UI.
Suggestion:
Would it be feasible to add either:
- A separate global "Autostart Order" view (independent of folder structure) where all containers can be freely drag-and-drop reordered regardless of which folder they're visually grouped in, or
- An option per-container to set an explicit autostart priority number that overrides folder-based ordering
Either would let folder organization stay purely visual/organizational while autostart sequencing remains fully flexible.
Thanks for maintaining this plugin — it's been very useful!
Title: Feature request: allow container ordering across folder boundaries (for autostart sequencing)
Body:
Currently, drag-and-drop reordering and the resulting autostart sync only work within a single folder. Containers are grouped into folders primarily for organizational/visual purposes, but this means the actual Docker autostart order ends up tied to folder membership — you can reorder containers inside a folder, but you can't interleave containers from different folders into a single custom startup sequence.
Use case:
I organize containers into folders by function (Network, Database, Security, etc.), but I need a specific startup order that cuts across those folders — e.g., a DNS container from "Network", followed by one from "Security", followed by a database container from "Database". Right now this isn't possible without merging those containers into one folder, which breaks the organizational structure I want to keep for the UI.
Suggestion:
Would it be feasible to add either:
Either would let folder organization stay purely visual/organizational while autostart sequencing remains fully flexible.
Thanks for maintaining this plugin — it's been very useful!