This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
Introduce Zero downtime deployments #20
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FarisZR
force-pushed
the
main
branch
4 times, most recently
from
203c0eb
to
5c23358
Compare
FarisZR
force-pushed
the
main
branch
3 times, most recently
from
73a892c
to
f3bf40d
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds deployment parameters that make zero-downtime upgrades and auto rollback possible.
This of course excludes databases, which can not be replicated.
fix #3
NOT READY TO MERGE
there are few things missing