-
Notifications
You must be signed in to change notification settings - Fork 78
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
reverse-proxy is not reloaded if nginx template is modified #369
Labels
good first issue
Good for newcomers
Comments
do you have an idea @XciD? (not urgent) |
You need to use something like this: to re-trigger the deployment |
severo
added
good first issue
Good for newcomers
and removed
question
Further information is requested
labels
Jun 15, 2022
Moved to the internal tracker |
mattstern31
added a commit
to mattstern31/datasets-server-storage-admin
that referenced
this issue
Nov 11, 2023
* feat: 🎸 change nginx logs to JSON also: - add the content of the request body (useful to get the content of the webhooks) - automatically recreate the pod if the nginx configuration has changed. Closes huggingface/dataset-viewer#369, thanks @XciD * chore: 🤖 add an annotation to let elastic know logs are json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the nginx template config is modified, it's correctly mounted in the pod, you can check with:
But I don't think the nginx process is reloaded, and I don't see a way to easily check if it is or not (https://serverfault.com/a/361465/363977 is too hardcore, and gdb is not installed on the pod)
The text was updated successfully, but these errors were encountered: