You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My stacks are deployed as files on the server, though the files were always initialized by Komodo itself. When I delete the stack using Komodo, the stack folder (and the related .env and compose.yaml files) remain intact on the host. Is this an expected behaviour? If so is there a way for Komodo to delete the stack folder and related files when the stack is deleted in the web GUI?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
My stacks are deployed as files on the server, though the files were always initialized by Komodo itself. When I delete the stack using Komodo, the stack folder (and the related
.envandcompose.yamlfiles) remain intact on the host. Is this an expected behaviour? If so is there a way for Komodo to delete the stack folder and related files when the stack is deleted in the web GUI?Beta Was this translation helpful? Give feedback.
All reactions