CVSROOT: /cvs
Module name: ports
Changes by: [email protected] 2024/08/24 10:50:36
Log message:
import www/caddy 2.8.4
ok tb@
https://caddyserver.com/
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 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.
Status:
Vendor Tag: semarie
Release Tags: semarie_20240824
N ports/www/caddy/Makefile
N ports/www/caddy/distinfo
N ports/www/caddy/pkg/caddy.rc
N ports/www/caddy/pkg/PLIST
N ports/www/caddy/pkg/DESCR
N ports/www/caddy/files/Caddyfile
No conflicts created by this import
