Describe the bug
When config files are symlinks, rathole won't pickup any changes file pointed to by the symlink. This is needed to detect any changes that are made to a Kubernetes ConfigMap mounted to a rathole pod at a path.
To Reproduce
Steps to reproduce the behavior:
Create a test/config.toml
Create a symlink ln -s ./test/config.toml ./config.toml
Run rathole --server ./config.toml
Edit test/config.toml or config.toml to change the server config to bind_addr = "0.0.0.0:1333"
Observe changes are not picked up and rathole doesn't hot reload.
$ RUST_BACKTRACE=1 rathole ./server.toml
2024-05-01T13:34:09.659589Z INFO rathole::server: Listening at 0.0.0.0:2333
2024-05-01T13:34:09.659660Z INFO config_watcher{path="./server.toml"}: rathole::config_watcher: Start watching the config
Describe the bug When config files are symlinks, rathole won't pickup any changes file pointed to by the symlink. This is needed to detect any changes that are made to a Kubernetes ConfigMap mounted to a rathole pod at a path.
To Reproduce Steps to reproduce the behavior:
test/config.toml
ln -s ./test/config.toml ./config.toml
rathole --server ./config.toml
test/config.toml
orconfig.toml
to change the server config tobind_addr = "0.0.0.0:1333"
Configuration
Logs
No hot reload log even after changing the config
Environment:
rathole --version
output: