1. 23 Mar, 2018 1 commit
  2. 21 Mar, 2018 1 commit
  3. 13 Feb, 2018 1 commit
  4. 23 Sep, 2017 1 commit
  5. 02 Aug, 2017 1 commit
    • Matthew Holt's avatar
      Distinguishable exit codes · cbb85532
      Matthew Holt authored
      0: normal or expected exit
      1: error before server finished starting
      2: double SIGINT (force quit)
      3: error stopping with SIGQUIT
      4: shutdown callback(s) returned error(s)
      cbb85532
  6. 31 Jul, 2017 1 commit
    • Matthew Holt's avatar
      Fix force quit using SIGINT · 65bc696b
      Matthew Holt authored
      Only the outside function call is executed in a new goroutine when
      invoking 'go'. Oops. Force quits (2 SIGINTs) now work again.
      65bc696b
  7. 03 Jun, 2017 1 commit
  8. 28 Mar, 2017 1 commit
  9. 24 Jun, 2016 1 commit
    • Matthew Holt's avatar
      OnFirstStartup and OnFinalShutdown callbacks added · 15fa5cf2
      Matthew Holt authored
      OnStartup and OnShutdown callbacks now run as part of restarts, too.
      The startup and shutdown directives only run their commands NOT as part
      of restarts, as before. Some middleware that use OnStartup may need to
      switch to OnFirstStartup and implement OnFinalShutdown to do any cleanup
      as needed.
      15fa5cf2
  10. 04 Jun, 2016 1 commit
    • Matthew Holt's avatar
      Rewrote Caddy from the ground up; initial commit of 0.9 branch · ac4fa2c3
      Matthew Holt authored
      These changes span work from the last ~4 months in an effort to make
      Caddy more extensible, reduce the coupling between its components, and
      lay a more robust foundation of code going forward into 1.0. A bunch of
      new features have been added, too, with even higher future potential.
      
      The most significant design change is an overall inversion of
      dependencies. Instead of the caddy package knowing about the server
      and the notion of middleware and config, the caddy package exposes an
      interface that other components plug into. This does introduce more
      indirection when reading the code, but every piece is very modular and
      pluggable. Even the HTTP server is pluggable.
      
      The caddy package has been moved to the top level, and main has been
      pushed into a subfolder called caddy. The actual logic of the main
      file has been pushed even further into caddy/caddymain/run.go so that
      custom builds of Caddy can be 'go get'able.
      
      The HTTPS logic was surgically separated into two parts to divide the
      TLS-specific code and the HTTPS-specific code. The caddytls package can
      now be used by any type of server that needs TLS, not just HTTP. I also
      added the ability to customize nearly every aspect of TLS at the site
      level rather than all sites sharing the same TLS configuration. Not all
      of this flexibility is exposed in the Caddyfile yet, but it may be in
      the future. Caddy can also generate self-signed certificates in memory
      for the convenience of a developer working on localhost who wants HTTPS.
      And Caddy now supports the DNS challenge, assuming at least one DNS
      provider is plugged in.
      
      Dozens, if not hundreds, of other minor changes swept through the code
      base as I literally started from an empty main function, copying over
      functions or files as needed, then adjusting them to fit in the new
      design. Most tests have been restored and adapted to the new API,
      but more work is needed there.
      
      A lot of what was "impossible" before is now possible, or can be made
      possible with minimal disruption of the code. For example, it's fairly
      easy to make plugins hook into another part of the code via callbacks.
      Plugins can do more than just be directives; we now have plugins that
      customize how the Caddyfile is loaded (useful when you need to get your
      configuration from a remote store).
      
      Site addresses no longer need be just a host and port. They can have a
      path, allowing you to scope a configuration to a specific path. There is
      no inheretance, however; each site configuration is distinct.
      
      Thanks to amazing work by Lucas Clemente, this commit adds experimental
      QUIC support. Turn it on using the -quic flag; your browser may have
      to be configured to enable it.
      
      Almost everything is here, but you will notice that most of the middle-
      ware are missing. After those are transferred over, we'll be ready for
      beta tests.
      
      I'm very excited to get this out. Thanks for everyone's help and
      patience these last few months. I hope you like it!!
      ac4fa2c3
  11. 10 Jan, 2016 1 commit
  12. 15 Nov, 2015 2 commits
  13. 06 Nov, 2015 1 commit
  14. 26 Oct, 2015 1 commit