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
Currently, exoframe will build and deploy new container and remove the old one only after new one is up and running.
This works fine for majority of services, but some require removal of old container before starting the new one (e.g. telegram bots that can only have one connection to API).
We need to introduce new config property (e.g. deploymentStrategy?) that can be either default (or removeAfterDeploy) or removeBeforeDeploy.
Should be fairly trivial to implement.
The text was updated successfully, but these errors were encountered:
Currently, exoframe will build and deploy new container and remove the old one only after new one is up and running.
This works fine for majority of services, but some require removal of old container before starting the new one (e.g. telegram bots that can only have one connection to API).
We need to introduce new config property (e.g.
deploymentStrategy
?) that can be eitherdefault
(orremoveAfterDeploy
) orremoveBeforeDeploy
.Should be fairly trivial to implement.
The text was updated successfully, but these errors were encountered: