- 23 Oct, 2015 1 commit
-
-
xenolf authored
-
- 22 Oct, 2015 1 commit
-
-
Matthew Holt authored
-
- 21 Oct, 2015 4 commits
-
-
Matt Holt authored
letsencrypt: Simplify timing mechanism for checking renewals
-
Matthew Holt authored
Conflicts: config/letsencrypt/letsencrypt.go
-
Matthew Holt authored
-
Matthew Holt authored
-
- 20 Oct, 2015 1 commit
-
-
xenolf authored
-
- 19 Oct, 2015 3 commits
-
-
Matthew Holt authored
User can specify 'tls off" in Caddyfile to force-disable automatic HTTPS configuration
-
Matthew Holt authored
-
Matthew Holt authored
-
- 18 Oct, 2015 10 commits
-
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
- 17 Oct, 2015 7 commits
-
-
Matthew Holt authored
Also added ServerBlockHostIndex
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
Also more comments and starting to clean up code
-
Matthew Holt authored
Code is a huge mess; much cleanup to follow.
-
- 16 Oct, 2015 5 commits
-
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
Conflicts: config/config.go
-
Matthew Holt authored
-
Matthew Holt authored
This way, Setup functions have access to the list of hosts that share the server block, and also, if needed for some reason, the index of the server block in the input
-
- 15 Oct, 2015 5 commits
-
-
Matthew Holt authored
-
Matthew Holt authored
-
Matthew Holt authored
startup and shutdown commands should only be executed once per appearance in the Caddyfile (naturally meaning once per server block). Notice that we support multiple occurrences of startup and shutdown in the same server block by building the callback array incrementally as we parse the Caddyfile, then we append all the callbacks all at once. Quite literally, the OncePerServerBlock function executes only once per server block!
-
Matthew Holt authored
If each server block had only one sync.Once then all directives would refer to it and only the first directive would be able to use it! So this commit changes it to a map of sync.Once instances, keyed by directive. So by creating a new map for every server block, each directive in that block can get its own sync.Once which is exactly what is needed. They won't step on each other this way.
-
Matthew Holt authored
Turns out having each server block share a single server.Config during initialization when the Setup functions are being called was a bad idea. Sure, startup and shutdown functions were only executed once, but they had no idea what their hostname or port was. So here we revert to the old way of doing things where Setup may be called multiple times per server block (once per host associated with the block, to be precise), but the Setup functions now know their host and port since the config belongs to exactly one virtualHost. To have something happen just once per server block, use OncePerServerBlock, a new function available on each Controller.
-
- 14 Oct, 2015 3 commits
-
-
Matthew Holt authored
-
Matt Holt authored
Add tests for command splitting and fix root tests on Windows
-
Matt Holt authored
Fix test failures on Windows.
-