go: Bump ports for go124 update

Bump all go ports for yesterday's releases

www/caddy: Update to 2.9.0

www/caddy, www/caddy-custom: Fix rc(8) instructions

I had 'service enable caddy' instead of 'service caddy enable' in
caddy.in, because I get it wrong so often that I had to write a
wrapper service() function in my shell.

Ludovic submitted a patch for this 5 months ago, but it went into
the same cerebral black hole as the order of service arguments.

PR:		280127
Reported by:	Ludovic Hirlimann

all: Bump after lang/go121 update

all: Bump after lang/go121 update

all: Bump after lang/go121 update

MFH:		2024Q2

www/caddy-custom: fix typo in 'caddy.in'

www/caddy,www/caddy-custom: Update to 2.8.1

Release notes:
https://github.com/caddyserver/caddy/releases/tag/v2.8.0
https://github.com/caddyserver/caddy/releases/tag/v2.8.1

all: Bump after lang/go121 update

MFH:		2024Q2

www/caddy-custom: Fix descr typo

all: Bump after lang/go121 update

MFH:		2024Q2

lang/go: Change DEFAULT to 1.21

PR:		277776
Approved by:	portmgr (exp-run)

all: Bump PORTREVISION after lang/go* update

PR:		276530

www/caddy{,-custom}: chown caddy.log to caddy user/group

We have set caddy.log to root:wheel, which works for the default case
of running caddy as root.

When caddy is run as a non-root users, caddy.log can't actually be
written to. Instead, chown caddy.log to the caddy user/group so that
it can be written to.

PR:		276150

www/caddy{,-custom}: Fix start/stop with admin API disabled

Caddy largely relies on the admin API for state control, like
start/stop/reload. However, the admin API endpoints are inherently
a security risk.

Although the admin API is enabled by default, many users may choose
to disable it. However, the rc(8) script then needs an alternative
approach to controlling the daemon.

We already sortof supported signal-based control, but it didn't always
work, because there are multiple error messages that indicate that
the admin API is disabled (and none of them actually say that in a clear
way).

This commit fixes start and stop with the admin API disabled. The
reload command (and reloadssl) still require the admin API to be
enabled and will fail if the admin API is disabled.

PR:		255106
Submitted by:	scf

all: Bump PORTREVISION after lang/go* update

PR:		274405

www/caddy-custom: Improve admin API endpoint and recommend www:www

all: Bump PORTREVISION after lang/go* update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after lang/go{119,120} update

www/caddy{,-custom}: Fix startup with JSON configuration

Caddy supports a wide number of configuration file formats, including
its built-in "Caddyfile" format, and the "native" format is JSON.

When anything other than the native JSON format is used, caddy needs to
be passed the --adapter [formatname] flag (though it automatically
handles the case where the config filename is Caddyfile). However, as
JSON is the native format, there is no "json" adapter.

The added patch drops the --adapter flag when caddy_adapter is "json".

PR:		270120

all: Bump PORTREVISION after Go ports update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after GO_DEFAULT update.

all: Bump PORTVERSION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

www/caddy-custom: Fix path to Caddyfile

www/caddy-security: Hook to the build and mark NO_PACKAGE

Unhooked ports get removed by a reaper script.

www/caddy-custom: Add port

This port allows you to build a version of the caddy webserver
using whichever plugins you desire. To do so, it uses the
official build mechanism, xcaddy (from the www/xcaddy port).

However, this requires network access.

To use this port, you'll need to add
ALLOW_NETWORKING_PACKAGES="caddy-custom" to your poudriere.conf.
Make really really REALLY sure you understand the implications
of doing this. If you use xcaddy, then there really isn't any
other actual implication, but I'm using my scary voice to
discourage people from shooting themselves in the foot.