-
Notifications
You must be signed in to change notification settings - Fork 617
Configuration
One of the main objectives of fabio is that you do not have to configure it to do its job.
If you run fabio next to a consul agent and your services are configured properly all you have to do is start it and forget about it.
By default fabio listens on port 9999
for HTTP traffic and uses
consul on localhost:8500
as the default registry backend.
Depending on your environment or requirements you may want to configure additional listeners, different backends, enable metrics reporting or change other configuration parameters. For this, please check the well documented fabio.properties file.
Each property value can also be configured via a corresponding environment variable which has the dots replaced with underscores.
Starting with version 1.2 parameters can also be specified on the command line. Arguments are parsed in the following order:
- properties file
- environment variable
- command line argument
# fabio.properties
metrics.target = stdout
# correspondig env var (no prefix)
metrics_target=stdout ./fabio
# env var with FABIO_ prefix (>= 1.2)
FABIO_metrics_target=stdout ./fabio
# env var with FABIO_ prefix (case-insensitive) (>= 1.2)
FABIO_METRICS_TARGET=stdout ./fabio
# command line argument (>= 1.2)
./fabio -metrics.target stdout
- Home
- Quickstart
- Installation
- Verifying Releases
- Configuration
- Binding to low ports
- Deployment
-
Features
- Access Logging ⭐️
- Certificate Stores
- Compression
- Circonus Support
- DataDog Support
- Docker Support
- Dynamic Reloading
- Graceful Shutdown
- Graphite Support
- HTTP Header
- HTTPS Upstream
- Metrics Support
- Path Stripping
- PROXY Protocol
- Request Debugging
- Request Tracing
- SSE Support
- StatsD Support
- TCP Proxy ⭐️
- TCP+SNI Support
- Traffic Shaping
- Vault Integration
- Websockets
- Web UI
- Performance
- Service Configuration
- Routing
- Debugging
- Contributing
- Why fabio?