Skip to content

Conversation

stevapple
Copy link
Contributor

Closes #1

Copy link
Member

@iBug iBug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really necessary to watch the config file, instead of only reload on request (e.g. SIGHUP)?

@stevapple
Copy link
Contributor Author

@iBug This is how I intended to use the reload feature with Kubernetes (by updating a ConfigMap-mapped file).

For bare-metal deployment, I believe we need a dedicated "daemon" program that handles a background process, in that way we can reload configs on-demand (eg. like NGINX).

@iBug
Copy link
Member

iBug commented Sep 2, 2024

Perhaps your use case is better covered by a separate CLI tool that monitors the file and sends signals. Doing this from within the server program itself seems weird to me. Remember this is server config, not applicatio data.

@stevapple
Copy link
Contributor Author

stevapple commented Sep 2, 2024

I would say it looks like a very common pattern in the K8s world, eg. in kube-proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configuration reload support

2 participants