Change local docker-compose setup
#824
Merged
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
2ae2bbe to
ab2259f
Compare
So that the healthcheck can run as the `postgres` user and not spam the Postgres logs with connection failure errors when the health check attempts to connect as the `root` user.
Set a `start_period` and a `start_interval` to ensure that the healthcheck quickly notices that Postgres is ready after startup. Thereafter, set the `interval` to 24h because we don't care about ongoing healthchecks in the local dev environment.
ab2259f to
0fa92a4
Compare
kvch
approved these changes
May 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make a couple of changes to the local
docker-composesetup:Run local the postgres container as user
postgres:Edit healthcheck settings to avoid repeated health checks after the container has started: