1. 06 Jun, 2016 4 commits
  2. 05 Jun, 2016 2 commits
  3. 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
  4. 03 Jun, 2016 5 commits
  5. 02 Jun, 2016 2 commits
  6. 29 May, 2016 2 commits
  7. 27 May, 2016 2 commits
  8. 25 May, 2016 1 commit
  9. 24 May, 2016 2 commits
  10. 21 May, 2016 1 commit
  11. 20 May, 2016 1 commit
  12. 15 May, 2016 1 commit
  13. 14 May, 2016 2 commits
  14. 12 May, 2016 3 commits
    • W. Mark Kubacki's avatar
      Merge pull request #817 from mholt/systemd-service-file · e516aebc
      W. Mark Kubacki authored
      Provides some more guidelines to operators on how to avoid running Caddy as root.
      
      Introduces an user www-data, which really is a placeholder. Such an user with the same UID/GID combination is created on the most popular Linux distribution. I trust any operator can spot the difference to his/her distro and adjust the unit file.
      
      User nobody is not used here to avoid two easy pitfalls: Such an user should not be able to access private keys (for TLS), and should not write private keys (we would do that with Letsencrypt).
      e516aebc
    • W-Mark Kubacki's avatar
      systemd: Run caddy with even less privileges and more confined · da8ae9e5
      W-Mark Kubacki authored
      The exemplary unit file for systemd is intentionally redundant at times, for
      example dropping privileges which an unprivileged user "www-data" did not have
      in the first place: To aid as fallback in case the file gets copied and an
      operator setting UID to 0 (which reportedly happened in the past).
      da8ae9e5
    • W-Mark Kubacki's avatar
      systemd, README: Edit for clarity · d377c79a
      W-Mark Kubacki authored
      d377c79a
  15. 07 May, 2016 4 commits
  16. 05 May, 2016 3 commits
  17. 04 May, 2016 1 commit
  18. 03 May, 2016 1 commit
  19. 01 May, 2016 2 commits