Files
computer-playbook/cli/contributing/network/README.md
T
kevinveenbirkenbachandClaude Opus 5 fcc98bcad1 fix(docs): require a README behind every directory link
The lint accepted a link that resolved to a file or a directory. myst
builds a document reference only when the target is_file(), so a link to
a directory without a README is a bare file listing on GitHub and a dead
cross-reference in the documentation build. It now reports which of the
two reasons applies.

The tightened rule found 41 links. Where a README backs the directory,
bd15eae9fa's resolver carries the link and it stays. Where none exists,
the link becomes a code span rather than an invented README: 15 of them
point at a role's meta/addons/, whose addon table already sits below the
sentence, and the rest at code directories such as utils/ or
cli/administration/deploy/runner/.

The changed sentences are msgids, so these entries return to the
translator on the next extract.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-25 18:42:23 +02:00

1.1 KiB

Network 🌐

Contributor-side network tooling: probe the live container network stack, suggest free per-role subnets, and suggest free host-bound ports.

Subcommands 🧭

Path Purpose
diagnose/ Run python -m cli.contributing.network.diagnose to print a structured DNS / TCP / TLS / PMTU report (IPv4 + IPv6) plus interface MTU, /etc/resolv.conf, /etc/hosts, proxy env vars, and CA bundle summaries from inside the running infinito container. Exposed as make diagnose-network.
address/ cli contributing network address suggest: propose the next free per-role IPv4 subnet(s) gap-first within the established umbrella blocks.
ports/ cli contributing network ports suggest: propose free host-bound ports inside PORT_BANDS.<scope>.<category>.