mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 12:23:22 +00:00
* docs(how-to): add guide for machines on a private network Users who already connect their machines with Tailscale, WireGuard, or a home network plus SSH can use skillshare across them without GitHub, but no page said so. Each piece already works: init --remote accepts any Git URL, the dashboard answers on an IP address or a trusted name, and mcp serve --http takes a bearer token on a private network. The new page covers a bare repository on one machine as the remote, opening another machine's dashboard through an SSH tunnel or its private address, and serving skills to agents on another machine. It also documents two traps found while running the flow end to end: a new bare repository's HEAD names master, so the next machine's init silently clones nothing until HEAD points at the pushed branch; and init --remote on a configured machine keeps the old remote. Translated for ja, ko, zh-Hans, and zh-Hant, with links from the cross-machine guide, its recipe, the ui reference, and the how-to index. * fix(how-to): point remote set-url at the skills repository The private-network guide told users with an existing remote to run git -C ~/.config/skillshare remote set-url. A setup made with plain init and connected to a remote later keeps its repository in the skills folder (git_root defaults to skills), so that command fails with "not a git repository" and the old remote stays. Checked in a container: after init then init --remote, .git is in ~/.config/skillshare/skills and init itself prints the skills path. The guide now says to run the command init prints, with ~/.config/skillshare/skills as the example. That path also works when the repository is at ~/.config/skillshare (a fresh init --remote), since git finds the parent repository. Fixed in the English page and the ja, ko, zh-Hans, and zh-Hant copies.