Keep backend running if database is empty #122
Conversation
This file contains hidden or 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
Release 1.0.0
Release 1.0.1
This makes it easier to setup Epimetheus on container environment where the database is not yet initialised. With exit() in place, backend container would keep terminating until database has data. Initialising system is easier when all containers keep running.
|
Hi. Can we get this merged? This container exit is really annoying in kubernetes environment, where is appears as constant crash loop. |
|
@Muusssi Can you look in to this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 makes it easier to setup Epimetheus on container environment
where the database is not yet initialised. With exit() in place,
backend container would keep terminating until database has data.
Initialising system is easier when all containers keep running.