-
Notifications
You must be signed in to change notification settings - Fork 118
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
Provide an option to crash the remultExpress server if ensureSchema fails #297
Comments
noam-honig
added a commit
that referenced
this issue
Nov 26, 2023
checkout remult@0.23.0-exp.29 |
@sefininio can you check it out and let me know if it's ok? |
Oh, I completely missed the previous comment (on the same freaking day! - amazing) |
Yes, that works! |
Great - closing the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When deploying to GCP, pods can't be loaded with dependencies on other pods - so the server might load before the DB instance and ensureSchema will fail silently. This scenario is better treated with
exit 1
so the pod will restart itself until success.Describe the solution you'd like
Add an optional option to remultExpress (defaults to false) that if true, will crash the server when ensureScheme fails.
The text was updated successfully, but these errors were encountered: