Maintenance: Drop zammad.ready file from docker entrypoint. #5087
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.
Zammad 6.3 will drop the
var/
folder, so that no share is needed any more for it. That's a good chance to improve the container waiting in the docker compose context as well.Rather than placing a file in the
var
share to signal readiness, we can simply call the rails stack and ask it to fail if migrations are pending. Other parts in thezammad-init
container such asTranslation.sync
can happen later and are not a requirement for services to start. This will also reduce start time / upgrade downtime significantly.zammad-helm will soon handle it in a similar way (see zammad/zammad-helm#243).