docs(readme): say Codespaces moves the server, not the rendering

The globe renders in the viewer's own browser, so a codespace does not
remove the need for local graphics. Retitle Path 4 accordingly.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Said TurkseverandClaude Opus 5.5 committed 2026-10-19 14:31:09 +01:00
1 parent f6fa5bf15b
commit 295e164fc3
1 file changed
+7 -5
+7 -5
View File
@@ -219,12 +219,14 @@ the container.
</details> </details>
### Path 4 — GitHub Codespaces (cloud, no local GPU) ### Path 4 — GitHub Codespaces (cloud, no local install)
Runs the same dev server in a cloud workspace, so integrated graphics and a Runs the same dev server in a cloud workspace, so Node and the dependencies
local GPU never come into it. GitHub Free includes 120 core-hours a month with never touch your machine. The globe still renders in your own browser, so it
no card on file — about 60 hours on the default 2-core machine. Org and needs the same graphics there as any other path. GitHub Free includes 120
Enterprise plans include no free quota; current terms and quotas apply. core-hours a month with no card on file — about 60 hours on the default 2-core
machine. Org and Enterprise plans include no free quota; current terms and
quotas apply.
1. Fork this repository, then open **your fork** on GitHub. 1. Fork this repository, then open **your fork** on GitHub.
2. Click the green **Code** button, the **Codespaces** tab, then **Create codespace on main**. 2. Click the green **Code** button, the **Codespaces** tab, then **Create codespace on main**.