{"schema_version":1,"metadata":{"branch":"release","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:02.361425+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/7.9/packages/amd64/sqlports-7.54.tgz","source_sha256":"2de00144847bf9da3a365be982f101dbb55d591ed7a915ea94984a16ab0e0404","package_count":12059,"source_kind":"sqlports"},"package":{"name":"caddy-2.11.2","path":"www/caddy","url":"/packages/release/www/caddy/","comment":"extensible HTTP/1-2-3 web server","homepage":"https://caddyserver.com/","maintainer":"The OpenBSD ports mailing-list <ports@openbsd.org>","description":"Caddy is most often used as an HTTPS server, but it is suitable for any\nlong-running Go program. First and foremost, it is a platform to run Go\napplications. Caddy \"apps\" are just Go programs that are implemented as Caddy\nmodules. Two apps -- tls and http -- ship standard with Caddy.\n\nCaddy apps instantly benefit from automated documentation, graceful on-line\nconfig changes via API, and unification with other Caddy apps.\n\nAlthough JSON is Caddy's native config language, Caddy can accept input from\nconfig adapters which can essentially convert any config format of your choice\ninto JSON: Caddyfile, JSON 5, YAML, TOML, NGINX config, and more.\n\nThe primary way to configure Caddy is through its API, but if you prefer config\nfiles, the command-line interface supports those too.\n\nCaddy exposes an unprecedented level of control compared to any web server in\nexistence. In Caddy, you are usually setting the actual values of the\ninitialized types in memory that power everything from your HTTP handlers and\nTLS handshakes to your storage medium. Caddy is also ridiculously extensible,\nwith a powerful plugin system that makes vast improvements over other web\nservers.\n\nTo wield the power of this design, you need to know how the config document is\nstructured. Please see our documentation site for details about Caddy's config\nstructure.\n\nNearly all of Caddy's configuration is contained in a single config document,\nrather than being scattered across CLI flags and env variables and a\nconfiguration file as with other web servers. This makes managing your server\nconfig more straightforward and reduces hidden variables/factors.\n\nFeatures:\n- Easy configuration with the Caddyfile\n- Powerful configuration with its native JSON config\n- Dynamic configuration with the JSON API\n- Config adapters if you don't like JSON\n- Automatic HTTPS by default\n  - ZeroSSL and Let's Encrypt for public names\n  - Fully-managed local CA for internal names & IPs\n  - Can coordinate with other Caddy instances in a cluster\n  - Multi-issuer fallback\n- Stays up when other servers go down due to TLS/OCSP/certificate-related issues\n- Production-ready after serving trillions of requests and managing millions of\n  TLS certificates\n- Scales to hundreds of thousands of sites as proven in production\n- HTTP/1.1, HTTP/2, and HTTP/3 all supported by default\n- Highly extensible modular architecture lets Caddy do anything without bloat\n","package_architecture":"amd64","stem":"caddy","readme":null,"dependencies":[{"path":"lang/go","type":"build","package_spec":"","url":"/packages/release/lang/go/"},{"path":"archivers/unzip","type":"build","package_spec":"","url":"/packages/release/archivers/unzip/"}],"reverse_dependencies":{"count":0,"url":null},"categories":["www","lang/go"],"flavors":[],"only_for_architectures":["aarch64","amd64","arm","i386","riscv64"],"not_for_architectures":[]}}