| Port details on branch 2023Q3 |
- caddy-custom Caddy (www/caddy) with customized plugins
- 2.6.4.6.0.3.3.2_9 www
 =0      2.6.4.6.0.3.3.2_9Version of this port present on the latest quarterly branch. - Maintainer: adamw@FreeBSD.org
- Port Added: 2023-08-04 15:02:22
- Last Update: 2023-09-08 14:39:12
- Commit Hash: 793b61c
- License: APACHE20
- WWW:
- https://caddyserver.com
- Description:
- This port will build a customized version of the caddy webserver
using plugins of your choice. You will need to rebuild this port
manually if one of your plugins gets updated.
Caddy is a high-performance webserver with a simple config format,
out-of-the-box HTTP/3 support, and automatica transparent ACME
certificate provisioning.
NOTE: THIS PORT BYPASSES EVERY SINGLE ONE OF FREEBSD'S CHECKSUM-
BASED DISTFILE TAMPERING DETECTION MECHANISMS. USE THIS AT YOUR
OWN PERIL (though the peril is exactly the same as using the
xcaddy port).
To make this work:
1) In /usr/local/etc/poudriere.conf, add the following:
ALLOW_NETWORKING_PACKAGES="caddy-custom"
You can skip this step if you're not building in poudriere.
2) Put your plugin list into make.conf (or
/usr/local/etc/poudriere.conf/make.conf):
.if ${.CURDIR:M*/www/caddy-custom*}
CADDY_CUSTOM_PLUGINS= github.com/caddy-dns/rfc2136 github.com/greenpau/caddy-security
.endif
If you have any other xcaddy build flags you want to set, put
them in XCADDY_ENV.
3) Profit
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- caddy-custom>0:www/caddy-custom
- Conflicts:
- CONFLICTS_INSTALL:
- To install the port:
- cd /usr/ports/www/caddy-custom/ && make install clean
- No package is available: Requires network access (see pkg-descr)
- PKGNAME: there is no package for this port: NO_PACKAGE = Requires network access (see pkg-descr)
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- xcaddy : www/xcaddy
- go120 : lang/go120
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- www_caddy-custom
- USES:
- go:no_targets
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
- There is no master site for this port.
|
Number of commits found: 2
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
2.6.4.6.0.3.3.2_9
08 Sep 2023 14:39:12
 |
Dmitri Goutnik (dmgk) |
all: Bump PORTREVISION after lang/go120 update
Approved by: ports-secteam (blanket) |
2.6.4.5.0.3.3.1_8
04 Aug 2023 14:36:07
|
Dmitri Goutnik (dmgk) |
all: Bump PORTREVISION after lang/go{119,120} update
Approved by: ports-secteam (blanket) |
Number of commits found: 2
|
As an Amazon Associate I earn from qualifying purchases.