Nuke pre-generation.  This may come back in the form of a more general
caching layer at some later stage.

Nuke index generation.  This should likely be rethought and re-implemented.

Caddy recovers panics that occur in the middleware stack so this is not a risk to process termination. This way is also preferable to hiding the error. See https://github.com/mholt/caddy/commit/3faad41b437c48cea37863123fab425169bc0c6e#commitcomment-17035158

Easier parallelism and more control over platforms we build for, but
more importantly, we can do parallel builds using the build script which
properly embeds version information into the binaries. We also produce
the archive files ourselves and in parallel rather than using external
tar and zip commands.

Flush every 250ms. This should keep latency somewhat low but there is
still buffering; maybe in the future we can make this configurable.

Handle host names case insensitively.

RFC 3986 3.2.2: The host subcomponent is case-insensitive.

Extract restartInProc to its own file

Also testing commit signing again, different email this time.

This will help build server perform builds with copy of repo in a folder
outside the original git repo folder. Also testing signed commits on
GitHub.

Rename EC256,EC384 to P256,P384

revert to old Caddyfile on failed in-process restart

update README to include Docker container zzrot/alpine-caddy

updated README to include ZZROT's docker container that runs caddy on Alpine Linux inside of a Docker Container.

Fix for #721

Add Etag header

https: Faster tests

proxy: Allow mixed case Upgrade headers (WebSocket fix)

Caddy expects websocket to be completely lowercase.
Some applications send websocket upgrade headers like the following:
`Upgrade: WebSocket`

This change allows all variations of websocket.

tls: Customize key type with key_type

dist/init: caddy.conf for upstart