Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add alternate deployment strategy (remove-before-deploy) #320

Open
yamalight opened this issue Jun 29, 2022 · 2 comments
Open

Add alternate deployment strategy (remove-before-deploy) #320

yamalight opened this issue Jun 29, 2022 · 2 comments

Comments

@yamalight
Copy link
Contributor

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.

@dualizeo
Copy link

Doesn't Watchtower do this?

@yamalight
Copy link
Contributor Author

@dualizeo how would that help in updating project deployed with exoframe? 🤔

@yamalight yamalight removed this from the 7.0 milestone Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants