Auto import stacks #376
Replies: 3 comments 1 reply
-
Interested in that as well. The docs aren't really clear on this, I have set of directories, one per manually managed stack, with a docker-compose.yml file in each. How can I "ingest" these into Komodo? |
Beta Was this translation helpful? Give feedback.
-
Made some progress. For the periphery container to be able to pick up existing compose files, either the directory of that compose file, or the parent directory of multiple compose files needs to be mounted into the periphery container. e.g. if there is This is quite a chore when there are many stack dirs already (but there's #377) and of course there's the limitation of #305 - so all in all, it's not yet so efficient to migrate from an existing manually managed set of stacks. |
Beta Was this translation helpful? Give feedback.
-
@arminus @millerm1993 I've written a tool to generate Sync Resource TOML from many, existing compose-folder projects. It's not a one-click import solution but it is pretty much copy-paste to create Stacks using a Sync. https://foxxmd.github.io/komodo-import |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am testing out before migrating from Dockge and love the app so far! The only thing I cant figure out/I don't know if its a feature is the ability to auto-import a bunch of stacks from a directory.
In the docs it talks about the ability to "pick up a running project" does this imply auto-detecting/importing from a directory? I have found the "New Deployment" button when having a container selected, but I don't believe that picks up my existing docker-compose files (just that specific container).
Is this in the current feature set? Is this something that is appropriate to raise a issue for?
Beta Was this translation helpful? Give feedback.
All reactions