caddy/caddy
Matthew Holt 9e2cef38f6 Write pidfile only if server starts successfully
Whether the original parent process or a child process as part of a restart, the pidfile will not be written/changed until that process has started successfully. It is written every time caddy.Start() succeeds (may be reundant, but that's probably okay).
2015-11-14 18:00:24 -07:00
..
assets Minor test improvements 2015-10-27 12:53:31 -06:00
caddyfile caddyfile: Change JSON format to use arrays, not objects 2015-11-10 11:49:01 -07:00
letsencrypt Show message when activating HTTPS 2015-11-07 17:12:21 -07:00
parse checkDirectives must've slipped through the cracks in big merge 2015-11-05 17:14:47 -07:00
setup Merge pull request #333 from mholt/firststartup 2015-11-10 23:03:17 -07:00
caddy.go Write pidfile only if server starts successfully 2015-11-14 18:00:24 -07:00
caddy_test.go core: Start() blocks until servers finish starting 2015-10-30 00:19:43 -06:00
config.go Unexport internal types; improved markdown summaries 2015-11-09 07:45:37 -07:00
config_test.go Merge branch 'master' into letsencrypt 2015-11-02 20:26:55 -07:00
directives.go letsencrypt: Activate during config load just after tls directive 2015-11-01 09:46:23 -07:00
helpers.go Write pidfile only if server starts successfully 2015-11-14 18:00:24 -07:00
restart.go core: Fixed minor restart bug 2015-11-10 21:26:22 -07:00
restart_windows.go core: Refactoring POSIX-only code for build tags 2015-10-26 16:49:05 -06:00
sigtrap.go Don't truncate process log; more consistent output 2015-11-05 17:01:08 -07:00
sigtrap_posix.go core: Fixed minor restart bug 2015-11-10 21:26:22 -07:00