Proksi
  • 🚀General
    • Getting started
    • Performance
    • Motivations
    • Specifications
  • 💾Installation
    • Docker
    • Single binary
  • 📚Configuration
    • HCL
      • Functions
    • YAML
    • ENV
    • Logging
    • Auto Reload
    • Daemon
    • Redis
  • 🔀Routing
    • Upstreams
    • Headers
  • 🧩Plugins
    • Request ID
    • Basic Auth
    • OAuth2
  • đŸ“Ŋī¸Use cases
    • Cache
    • Docker swarm
  • đŸ›Šī¸Contributing
    • Repository
  • Github
  • Crates.io
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Configuration

Auto Reload

Proksi can be configured to automatically reload the configuration file when it changes. This can be useful when you want to change the configuration without restarting the service.

To enable auto reload, you can set the auto_reload key to true in the configuration file. The default value is false.

proksi.hcl
auto_reload {
  # Whether to enable auto reload (default: false)
  enabled = true
  # The interval (in seconds) to check for changes (default: 30)
  interval_secs = 5

  # extra paths to watch for changes (default: [])
  # This is useful if you are dealing with `import` in the configuration file
  # changes on those imports will trigger a reload on the main configuration
  # file and down.
  # This will only watch for .hcl files and ignore any other extension.
  paths = ["/etc/sites"]
}
PreviousLoggingNextDaemon

Last updated 10 months ago

Was this helpful?

📚