Infrastructure/caddy
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2024-12-23 22:27:38 -05:00
Code Issues Activity

Service file for systemd starts after all networks have gotten IP addresses

Browse source 
Unlike network.target the network-online.target guarantees that the network
devices are online.

If you bind to 0.0.0.0, [::], [::1], and/or 127.0.0.1 only that is enough to
proceed. But in case a particular IP is needed, like ${COREOS_PUBLIC_IPV4},
we require any IP assignments to have completed before Caddy's start. That
is achieved by depending on systemd-networkd-wait-online.service (which is
scheduled before network-online.target, then, automatically).
This commit is contained in:
W-Mark Kubacki 2016-03-18 12:36:54 +01:00
parent 6b801b111b
commit f1c1ea9905
2 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.gitattributes vendored Normal file
View file

@ -0,0 +1,4 @@
# files for systemd
*.path text eol=lf whitespace=blank-at-eol,space-before-tab,tab-in-indent,trailing-space,tabwidth=2
*.service text eol=lf whitespace=blank-at-eol,space-before-tab,tab-in-indent,trailing-space,tabwidth=2
*.timer text eol=lf whitespace=blank-at-eol,space-before-tab,tab-in-indent,trailing-space,tabwidth=2

4
dist/init/linux-systemd/caddy@.service vendored
View file

@ -4,7 +4,9 @@
[Unit] [Unit]
Description=Caddy HTTP/2 web server %I Description=Caddy HTTP/2 web server %I
Documentation=https://caddyserver.com/docs Documentation=https://caddyserver.com/docs
After=network.target After=network-online.target
Wants=network-online.target
Wants=systemd-networkd-wait-online.service
[Service] [Service]
; run user and group for caddy ; run user and group for caddy