115b877e1a
When using the default automation policy specifically, ap.Issuer would be nil, so we'd end up overwriting the ap.magic.Issuer's default value (after New()) with nil; this instead sets Issuer on the template before New() is called, and no overwriting is done. |
||
|---|---|---|
| caddyconfig | ||
| caddytest | ||
| cmd | ||
| modules | ||
| .gitignore | ||
| .golangci.yml | ||
| admin_test.go | ||
| admin.go | ||
| AUTHORS | ||
| azure-pipelines.yml | ||
| caddy.go | ||
| context_test.go | ||
| context.go | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| listeners_fuzz.go | ||
| listeners_test.go | ||
| listeners.go | ||
| logging.go | ||
| modules_test.go | ||
| modules.go | ||
| README.md | ||
| replacer_fuzz.go | ||
| replacer_test.go | ||
| replacer.go | ||
| sigtrap_nonposix.go | ||
| sigtrap_posix.go | ||
| sigtrap.go | ||
| storage.go | ||
| usagepool.go | ||
Caddy 2
This is the development branch for Caddy 2.
Caddy 2 is production-ready, but there may be breaking changes before the stable 2.0 release. Please test it and deploy it as much as you are able, and submit your feedback!
Caddy 2 is the web server of the Go community. We are looking for maintainers to represent the community! Please become involved with issues, PRs, our forum, sharing on social media, etc.
Every site on HTTPS
Caddy is an extensible server platform that uses TLS by default.
Download · Documentation · Community
Menu
Powered by
Build from source
Note: These steps will not embed proper version information. For that, please follow the instructions below for building with plugins (you do not have to add any plugins).
Requirements:
- Go 1.14 or newer
- Do NOT disable Go modules (
export GO111MODULE=auto)
Download the v2 source code:
$ git clone -b v2 "https://github.com/caddyserver/caddy.git"
Build:
$ cd caddy/cmd/caddy/
$ go build
That will put a caddy(.exe) binary into the current directory.
If you encounter any Go-module-related errors, try clearing your Go module cache ($GOPATH/pkg/mod) or Go package cache ($GOPATH/pkg) and read the Go wiki page about modules for help. If you have issues with Go modules, please consult the Go community for help. But if there is an actual error in Caddy, please report it to us.
Building with plugins and/or version information
Caddy is extensible with plugins. Plugins are added at compile-time, so all Caddy binaries are static (self-contained) and portable.
Instructions for doing this are also given in comments in cmd/caddy/main.go which you can copy and use as a template.
- Create a new folder:
mkdir caddy - Change into it:
cd caddy - Copy Caddy's main.go into the empty folder. Add imports for any plugins you want to include.
- Run:
go mod init caddy - Run:
go get github.com/caddyserver/caddy/v2@TAGreplacingTAGwith the latest v2 tag. (Won't be necessary after stable 2.0 release.) - Run:
go build
Congrats, you now have a custom Caddy build with proper version information!
Quick start
The Caddy website has documentation that includes tutorials, quick-start guides, reference, and more.
We recommend that all users do our Getting Started guide to become familiar with using Caddy.
If you've only got a few minutes, the website has several quick-start tutorials to choose from! However, after finishing a quick-start tutorial, please read more documentation to understand how the software works. 🙂
Overview
Caddy is most often used as an HTTPS server, but it is suitable for any long-running Go program. First and foremost, it is a platform to run Go applications. Caddy "apps" are just Go programs that are implemented as Caddy modules. Two apps -- tls and http -- ship standard with Caddy.
Caddy apps instantly benefit from automated documentation, graceful on-line config changes via API, and unification with other Caddy apps.
Although JSON is Caddy's native config language, Caddy can accept input from config adapters which can essentially convert any config format of your choice into JSON: Caddyfile, JSON 5, YAML, TOML, NGINX config, and more.
The primary way to configure Caddy is through its API, but if you prefer config files, the command-line interface supports those too.
Caddy exposes an unprecedented level of control compared to any web server in existence. In Caddy, you are usually setting the actual values of the initialized types in memory that power everything from your HTTP handlers and TLS handshakes to your storage medium. Caddy is also ridiculously extensible, with a powerful plugin system that makes vast improvements over other web servers.
To wield the power of this design, you need to know how the config document is structured. Please see the our documentation site for details about Caddy's config structure.
Nearly all of Caddy's configuration is contained in a single config document, rather than being scattered across CLI flags and env variables and a configuration file as with other web servers. This makes managing your server config more straightforward and reduces hidden variables/factors.
Full documentation
Our website has complete documentation:
The docs are also open source. You can contribute to them here: https://github.com/caddyserver/website
Getting help
-
We strongly recommend that all professionals or companies using Caddy get a support contract through Ardan Labs before help is needed.
-
Individuals can exchange help for free on our community forum at https://caddy.community. Remember that people give help out of their spare time and good will. The best way to get help is to give it first!
Please use our issue tracker only for bug reports and feature requests, i.e. actionable development items (support questions will usually be referred to the forums).
About
The name "Caddy" is trademarked. The name of the software is "Caddy", not "Caddy Server" or "CaddyServer". Please call it "Caddy" or, if you wish to clarify, "the Caddy web server". Caddy is a registered trademark of Light Code Labs, LLC.
- Project on Twitter: @caddyserver
- Author on Twitter: @mholt6