caddy/caddyfile
Matthew Holt d2be213e10
Import paths now relative to Caddyfile (closes #867)
This is inconsistent with the other directives, but import is a special
case and frankly the behavior of import shouldn't change depending
on the directory from which you run caddy. Breaking change but I think
it's for the better, and best to do it now before 1.0.
2016-06-28 22:39:29 -06:00
..
testdata Rewrote Caddy from the ground up; initial commit of 0.9 branch 2016-06-04 17:00:29 -06:00
dispenser_test.go Rewrote Caddy from the ground up; initial commit of 0.9 branch 2016-06-04 17:00:29 -06:00
dispenser.go More tests, several fixes and improvements; export caddyfile.Token 2016-06-04 22:50:23 -06:00
json_test.go Rewrote Caddy from the ground up; initial commit of 0.9 branch 2016-06-04 17:00:29 -06:00
json.go Set host and port on address if specified via flag (fixes #888) 2016-06-20 18:25:42 -06:00
lexer_test.go More tests, several fixes and improvements; export caddyfile.Token 2016-06-04 22:50:23 -06:00
lexer.go More tests, several fixes and improvements; export caddyfile.Token 2016-06-04 22:50:23 -06:00
parse_test.go Import paths now relative to Caddyfile (closes #867) 2016-06-28 22:39:29 -06:00
parse.go Import paths now relative to Caddyfile (closes #867) 2016-06-28 22:39:29 -06:00