mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 5
af605b049f
RFC 6761 reserves .test for testing and .example for documentation, and the project's own domain was doing both jobs under the documentation name. It is what default.env hands every local deploy and what the test fixtures assert against, so it is a testing name. Rename it wherever it stands for the running machine: the environment defaults, the development inventory, the workspace and trust scripts, the test suites, and the four documents that describe real behaviour - the DNS mapping to loopback, the browser CA trust, WSL2 resolution. Those documents would have started lying the moment default.env changed. The sandbox allowlist moves with them, since egress is matched per pattern and nothing resolves the old name any more, and the sandbox document that mirrors that list follows it. Two places keep .example on purpose: the link-style sample in the documentation guide, which is documentation about documentation, and every generic fixture name elsewhere in the suite - a.example, foo.example and their kin. Those are a larger sweep of their own and are not touched here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Windows (WSL2)
On Windows, use WSL2 as the development environment and run the repository commands inside WSL2, not directly in PowerShell.
Use Ubuntu 24.04 with Docker Desktop WSL2 integration, enable systemd, and expect a few Windows-specific follow-up steps around certificate authority (CA) trust and local name resolution.
Keep these WSL2 specifics in mind:
- Trust the generated CA in Windows, not only inside WSL2.
- If
*.infinito.testdoes not resolve correctly, check Windows-side DNS or hosts configuration. - If container or security setup behaves differently than on Linux, the WSL2 guide covers the usual Docker Buildx, DNS, and AppArmor-related workarounds.
More information and detailed instructions here.