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
fix: gotrue config persistence for AIO #961
Conversation
pcnc
commented
May 1, 2024
- Fixes GoTrue losing its config on subsequent restarts
- Replaces gotrue's and fail2ban's commands to ensure external processes don't restart the service's process itself
- Adds flag to disable pgbouncer
docker/all-in-one/entrypoint.sh
Outdated
@@ -80,10 +80,23 @@ function enable_lsn_checkpoint_push { | |||
} | |||
|
|||
function disable_fail2ban { | |||
sed -i "s/command=.*/command=sleep 1/" /etc/supervisor/services/fail2ban.conf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a danger here that this sleep isn't long enough.
By default if a program doesn't stay up for 1 second, it is considered a failure and it will restart
I would set this to 2, or set startsecs to 0 - but startsecs isn't in the config file rn
from the manual
startsecs
The total number of seconds which the program needs to stay running after a startup to consider the start successful (moving the process from the STARTING state to the RUNNING state). Set to 0 to indicate that the program needn’t stay running for any particular amount of time.
Note
Even if a process exits with an “expected” exit code (see exitcodes), the start will still be considered a failure if the process exits quicker than startsecs.
Default: 1
Required: No.
Introduced: 3.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, nice catch. Will set it to 5
just to make sure it doesn't have any side effects
may need to update testinfra tests |