vgk/ungleich-staticcms
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

add lektor to IPv6 enabled apps

Browse source
This commit is contained in:
Nico Schottelius 2019-09-25 21:26:29 +09:00
parent bf03e1497d
commit 5d3717dfb4
1 changed files with 16 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
content/u/blog/how-to-enable-ipv6-in-applications/contents.lr
View file

@ -17,7 +17,7 @@ various applications.
## nginx ## nginx
The web server nginx by default only listens to IPv4 if you use The web server [nginx](https://nginx.org/) by default only listens to IPv4 if you use
the standard `listen *:80;` directive. To enable IPv6, use the standard `listen *:80;` directive. To enable IPv6, use
`listen [::]:80;`. So for a dual stack server, your configuration `listen [::]:80;`. So for a dual stack server, your configuration
could look as follows: could look as follows:
@ -36,7 +36,8 @@ server {
## haproxy ## haproxy
There are various interesting configuration options in HAProxy related There are various interesting configuration options in
[HAProxy](https://www.haproxy.org/) related
to IPv6. Let's have a look at each of them! to IPv6. Let's have a look at each of them!
To enable IPv6 transport for the local logging, use `log [::1]` in the To enable IPv6 transport for the local logging, use `log [::1]` in the
@ -97,6 +98,19 @@ backend httpsipv6
server twitter.com ipv4@twitter.com server twitter.com ipv4@twitter.com
``` ```
## Lektor
The static CMS lektor by default serves on IPv4. To serve on IPv6
localhost use `-h ::1`, to be globally reachable use `-h ::`.
```
# Serve on IPv6 localhost
% lektor serve -h ::1
# Serve on IPv6 (globally reachable)
% lektor serve -h ::
```
## Other applications ## Other applications