homelab/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix whitespaces

Browse source
This commit is contained in:
Chulki Lee 2017-09-07 03:02:03 -07:00 • committed by Traefiker
parent 924e82ab0c
commit 8c5514612f
36 changed files with 126 additions and 126 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/basics.md
View file

@ -355,7 +355,7 @@ requests periodically carried out by Traefik. The check is defined by a path
appended to the backend URL and an interval (given in a format understood by [time.ParseDuration](https://golang.org/pkg/time/#ParseDuration)) specifying how
often the health check should be executed (the default being 30 seconds).
Each backend must respond to the health check within 5 seconds.
By default, the port of the backend server is used, however, this may be overridden.
By default, the port of the backend server is used, however, this may be overridden.
A recovering backend returning 200 OK responses again is being returned to the
LB rotation pool.
@ -500,9 +500,9 @@ Usage:
traefik [command] [--flag=flag_argument]
```
List of Træfik available commands with description :                                                             
List of Træfik available commands with description :
- `version` : Print version 
- `version` : Print version
- `storeconfig` : Store the static traefik configuration into a Key-value stores. Please refer to the [Store Træfik configuration](/user-guide/kv-config/#store-trfk-configuration) section to get documentation on it.
- `bug`: The easiest way to submit a pre-filled issue.
- `healthcheck`: Calls traefik `/ping` to check health.

4
docs/benchmarks.md
View file

@ -65,8 +65,8 @@ http {
keepalive_requests 10000;
types_hash_max_size 2048;
open_file_cache max=200000 inactive=300s;
open_file_cache_valid 300s;
open_file_cache max=200000 inactive=300s;
open_file_cache_valid 300s;
open_file_cache_min_uses 2;
open_file_cache_errors on;

2
docs/configuration/backends/boltdb.md
View file

@ -33,4 +33,4 @@ prefix = "/traefik"
# Optional
#
filename = "boltdb.tmpl"
```
```

2
docs/configuration/backends/consul.md
View file

@ -113,4 +113,4 @@ Additional settings can be defined using Consul Catalog tags:
| `traefik.frontend.rule=Host:test.traefik.io` | Override the default frontend rule (Default: `Host:{{.ServiceName}}.{{.Domain}}`). |
| `traefik.frontend.passHostHeader=true` | Forward client `Host` header to the backend. |
| `traefik.frontend.priority=10` | Override default frontend priority |
| `traefik.frontend.entryPoints=http,https` | Assign this frontend to entry points `http` and `https`. Overrides `defaultEntryPoints`. |
| `traefik.frontend.entryPoints=http,https` | Assign this frontend to entry points `http` and `https`. Overrides `defaultEntryPoints`. |

2
docs/configuration/backends/docker.md
View file

@ -168,4 +168,4 @@ exposedbydefault = false
!!! warning
when running inside a container, Træfik will need network access through:
`docker network connect <network> <traefik-container>`
`docker network connect <network> <traefik-container>`

2
docs/configuration/backends/dynamodb.md
View file

@ -53,7 +53,7 @@ SecretAccessKey = "123"
Endpoint = "http://localhost:8080"
```
Items in the `dynamodb` table must have three attributes:
Items in the `dynamodb` table must have three attributes:
- `id` (string): The id is the primary key.
- `name`(string): The name is used as the name of the frontend or backend.

2
docs/configuration/backends/file.md
View file

@ -148,7 +148,7 @@ filename = "rules.toml"
## Multiple .toml Files
You could have multiple `.toml` files in a directory:
```toml
[file]
directory = "/path/to/config/"

2
docs/configuration/backends/rancher.md
View file

@ -101,7 +101,7 @@ secretKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
!!! note
If Traefik needs access to the Rancher API, you need to set the `endpoint`, `accesskey` and `secretkey` parameters.
To enable traefik to fetch information about the Environment it's deployed in only, you need to create an `Environment API Key`.
This can be found within the API Key advanced options.

2
docs/configuration/backends/web.md
View file

@ -86,7 +86,7 @@ You can enable Traefik to export internal metrics to different monitoring system
- DataDog
```toml
# DataDog metrics exporter type
# DataDog metrics exporter type
[web.metrics.datadog]
Address = "localhost:8125"
Pushinterval = "10s"

2
docs/configuration/backends/zookeeper.md
View file

@ -35,4 +35,4 @@ prefix = "traefik"
# filename = "zookeeper.tmpl"
```
Please refer to the [Key Value storage structure](/user-guide/kv-config/#key-value-storage-structure) section to get documentation on traefik KV structure.
Please refer to the [Key Value storage structure](/user-guide/kv-config/#key-value-storage-structure) section to get documentation on traefik KV structure.

28
docs/configuration/commons.md
View file

@ -154,7 +154,7 @@ logLevel = "ERROR"
### Access Logs
Access logs are written when `[accessLog]` is defined.
Access logs are written when `[accessLog]` is defined.
By default it will write to stdout and produce logs in the textual Common Log Format (CLF), extended with additional fields.
To enable access logs using the default settings just add the `[accessLog]` entry.
@ -197,7 +197,7 @@ This allows the logs to be rotated and processed by an external program, such as
Custom error pages can be returned, in lieu of the default, according to frontend-configured ranges of HTTP Status codes.
In the example below, if a 503 status is returned from the frontend "website", the custom error page at http://2.3.4.5/503.html is returned with the actual status code set in the HTTP header.
Note, the `503.html` page itself is not hosted on traefik, but some other infrastructure.
Note, the `503.html` page itself is not hosted on traefik, but some other infrastructure.
```toml
[frontends]
@ -275,13 +275,13 @@ The configured status code ranges are inclusive; that is, in the above example,
# If zero, no timeout exists.
# Can be provided in a format supported by [time.ParseDuration](https://golang.org/pkg/time/#ParseDuration) or as raw
# values (digits). If no units are provided, the value is parsed assuming seconds.
#
#
# Optional
# Default: "0s"
#
#
# readTimeout = "5s"
# writeTimeout is the maximum duration before timing out writes of the response. It covers the time from the end of
# writeTimeout is the maximum duration before timing out writes of the response. It covers the time from the end of
# the request header read to the end of the response write.
# If zero, no timeout exists.
# Can be provided in a format supported by [time.ParseDuration](https://golang.org/pkg/time/#ParseDuration) or as raw
@ -289,7 +289,7 @@ The configured status code ranges are inclusive; that is, in the above example,
#
# Optional
# Default: "0s"
#
#
# writeTimeout = "5s"
# idleTimeout is the maximum duration an idle (keep-alive) connection will remain idle before closing itself.
@ -310,30 +310,30 @@ The configured status code ranges are inclusive; that is, in the above example,
```toml
[forwardingTimeouts]
# dialTimeout is the amount of time to wait until a connection to a backend server can be established.
# dialTimeout is the amount of time to wait until a connection to a backend server can be established.
# If zero, no timeout exists.
# Can be provided in a format supported by [time.ParseDuration](https://golang.org/pkg/time/#ParseDuration) or as raw
# values (digits). If no units are provided, the value is parsed assuming seconds.
#
#
# Optional
# Default: "30s"
#
#
# dialTimeout = "30s"
# responseHeaderTimeout is the amount of time to wait for a server's response headers after fully writing the request (including its body, if any).
# responseHeaderTimeout is the amount of time to wait for a server's response headers after fully writing the request (including its body, if any).
# If zero, no timeout exists.
# Can be provided in a format supported by [time.ParseDuration](https://golang.org/pkg/time/#ParseDuration) or as raw
# values (digits). If no units are provided, the value is parsed assuming seconds.
#
# Optional
# Default: "0s"
#
#
# responseHeaderTimeout = "0s"
```
### Idle Timeout (deprecated)
Use [respondingTimeouts](/configuration/commons/#responding-timeouts) instead of `IdleTimeout`.
Use [respondingTimeouts](/configuration/commons/#responding-timeouts) instead of `IdleTimeout`.
In the case both settings are configured, the deprecated option will be overwritten.
`IdleTimeout` is the maximum amount of time an idle (keep-alive) connection will remain idle before closing itself.
@ -344,7 +344,7 @@ If no units are provided, the value is parsed assuming seconds.
```toml
# IdleTimeout
#
#
# DEPRECATED - see [respondingTimeouts] section.
#
# Optional
@ -388,7 +388,7 @@ filename = "my_custom_config_template.tpml"
The template files can be written using functions provided by:
- [go template](https://golang.org/pkg/text/template/)
- [go template](https://golang.org/pkg/text/template/)
- [sprig library](https://masterminds.github.io/sprig/)
Example:

2
docs/index.md
View file

@ -71,7 +71,7 @@ Run it and forget it!
You can have a quick look at Træfik in this [Katacoda tutorial](https://www.katacoda.com/courses/traefik/deploy-load-balancer) that shows how to load balance requests between multiple Docker containers.
Here is a talk given by [Emile Vauge](https://github.com/emilevauge) at [GopherCon 2017](https://gophercon.com).
You will learn Træfik basics in less than 10 minutes.
You will learn Træfik basics in less than 10 minutes.
[![Traefik GopherCon 2017](https://img.youtube.com/vi/RgudiksfL-k/0.jpg)](https://www.youtube.com/watch?v=RgudiksfL-k)

2
docs/user-guide/cluster.md
View file

@ -18,4 +18,4 @@ Once your Træfik configuration is uploaded on your KV store, you can start each
A Træfik cluster is based on a manager/worker model.
When starting, Træfik will elect a manager.
If this instance fails, another manager will be automatically elected.

2
docs/user-guide/kv-config.md
View file

@ -36,7 +36,7 @@ consul:
- "8301"
- "8301/udp"
- "8302"
- "8302/udp"
- "8302/udp"
whoami1:
image: emilevauge/whoami

10
docs/user-guide/swarm-mode.md
View file

@ -303,11 +303,11 @@ Wait, I thought we added the sticky flag to `whoami1`? Traefik relies on a cook
First you need to add `whoami1.traefik` to your hosts file:
```shell
if [ -n "$(grep whoami1.traefik /etc/hosts)" ];
then
echo "whoami1.traefik already exists (make sure the ip is current)";
else
sudo -- sh -c -e "echo '$(docker-machine ip manager)\twhoami1.traefik' >> /etc/hosts";
if [ -n "$(grep whoami1.traefik /etc/hosts)" ];
then
echo "whoami1.traefik already exists (make sure the ip is current)";
else
sudo -- sh -c -e "echo '$(docker-machine ip manager)\twhoami1.traefik' >> /etc/hosts";
fi
```