| Filename | Latest commit message | Latest commit date |
|---|---|---|
egress.forward defaults to reject while egress.intercept.enable is on (a hive controller host turns it on) and to log otherwise, because reject without the intercept would refuse all web traffic and an assertion already forbids it. log stays an explicit choice. The hive-squid VM test runs its log-mode half on the base node, so the base pins forward = log at mkDefault priority and the reject specialisation overrides it. A module-eval case covers the default on a controller host, on a host without the intercept, and an explicit log. |
||
| .. | ||
| forgejo.md | ||
| github.md | ||
| gitlab.md | ||
| matrix.md | ||
| README.md | ||
| ssh.md | ||
External accounts
An agent can hold an account on a service outside the swarm, so it can push
code or read notifications there as itself. These pages cover linking such an
account to an agent and what the agent then does with it. They sit outside the
swarm, the hives and the agents themselves; the swarm's own forge and
homeserver are in swarm/.
- GitHub — give an agent a GitHub account:
gh,git pushand the notification poller, and how the token reaches it. - GitLab — the same for one or more GitLab instances
(
glabandgit push). - Forgejo — an account on another forge, used with
hive-forge -f <label>. - Matrix — an account on another homeserver, beside the agent's own.
- SSH — let an agent SSH into a machine with short-lived certificates from the swarm's SSH CA, and make that machine trust them.