Index | Thread | Search

From:
Sebastien Marie <semarie@kapouay.eu.org>
Subject:
new: www/caddy
To:
ports@openbsd.org
Date:
Sat, 24 Aug 2024 14:02:41 +0200

Download raw body.

Thread
  • Sebastien Marie:

    new: www/caddy

Hi,

The attached tarball contains a port for caddy server
(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.


It reuses uid/gid 524 (from 2016).

diff /home/semarie/repos/openbsd/ports
commit - a4d48766a296eeb3f8ed9992966d7d7a1fd4612e
path + /home/semarie/repos/openbsd/ports
blob - 5104415dc091f405d9c26b9c73d49c1d2e7be77e
file + infrastructure/db/user.list
--- infrastructure/db/user.list
+++ infrastructure/db/user.list
@@ -32,7 +32,7 @@ id  user		group		port
 521 _exim		_exim		mail/exim
 522 _unboundexporter			sysutils/unbound_exporter
 523 _ffproxy		_ffproxy	www/ffproxy
-#524			_mail		mail/openwebmail
+524 _caddy		_caddy		www/caddy
 525 _quagga		_quagga		net/quagga
 526 _tomcat		_tomcat		www/tomcat
 527 _milter-regex	_milter-regex	mail/milter-regex

Comments or OK to import ?
-- 
Sebastien Marie