Replace SSH tutorial in README with wiki pages by OS
CI / Run Tests (push) Failing after 2s
CI / Export Windows (push) Has been skipped
CI / Export Linux (push) Has been skipped
CI / Export Android (push) Has been skipped
Test Suite / Unit Tests (GUT) (push) Failing after 2s
Test Suite / Integration Tests (push) Failing after 3s
Test Suite / Code Style Check (push) Failing after 2s
Test Suite / Security Scan (push) Failing after 1m1s
CI / Create Release (push) Has been skipped

Linux, macOS, Windows SSH setup guides moved to wiki. README becomes index with wiki links and breadcrumb to existing docs.
This commit is contained in:
2026-07-02 01:35:51 +08:00
parent ccd759da45
commit 625ff5ec69
4 changed files with 122 additions and 33 deletions
+9 -33
View File
@@ -4,46 +4,22 @@
>
> See in particular: [Skin Creation Workflow](./Skin-Creation-Workflow), [Nakama Deployment](./Nakama-Deployment), and [Patch Release Workflow](./Patch-Release-Workflow).
# Cloning from any tailnet machine
## SSH setup for cloning
## Prerequisites
- The remote machine must be on your tailnet (registered + can ping `100.85.x.x`)
- You must have an account on the Gitea instance (`http://git.klud.top`)
- You must have an SSH key on the remote machine (`ssh-keygen` if you don't)
All clones **must use SSH** over Tailscale. HTTPS is disabled on this instance.
## Step 1: Add your SSH key to Gitea
1. Open `http://git.klud.top/user/settings/keys` in browser
2. Paste the content of `~/.ssh/id_ed25519.pub` (or `id_rsa.pub`)
3. Click "Add Key"
Guides by operating system:
## Step 2: Test SSH reachability
- [Linux](/danchie/tekton/wiki/SSH-Setup-Linux)
- [macOS](/danchie/tekton/wiki/SSH-Setup-macOS)
- [Windows](/danchie/tekton/wiki/SSH-Setup-Windows)
Quick verification after setup:
```bash
ssh -T git@thunderobot -p 222
# Expected output: "Hello from Gitea!\n\nPlease come over!"
# If asked about fingerprint, type "yes" and press Enter
```
## Step 3: Clone a repo
Once verified, clone:
```bash
# Using tea CLI
tea repos clone --git-protocol ssh danchie/tekton
# Or plain git
git clone git@thunderobot:222/danchie/tekton.git
```
## Troubleshooting
- `ssh: connect to host thunderobot port 222: Connection refused`
→ Ensure the remote machine has `tailscale ping thunderobot` resolving to `100.93.226.13`
→ Ensure the host's port `222` is reachable from the remote (it's bound to `0.0.0.0:222` in Docker)
- `Permission denied (publickey)`
→ Your SSH key wasn't added via Gitea web UI
→ Run `ssh-add ~/.ssh/id_ed25519` if you use an agent
- `Host key verification failed`
→ Run `ssh -T git@thunderobot -p 222` interactively once to accept the fingerprint
## HTTPS is disabled
`DISABLE_HTTP_GIT = true` is set on the server. All clones MUST use SSH.
If you need to fetch via HTTPS for CI or other non-ssh environments, this must be remapped.
+36
View File
@@ -0,0 +1,36 @@
# SSH Setup — Linux
## Generate an SSH key
Open a terminal and run:
```bash
ssh-keygen -t ed25519 -C "your-name@example.com"
```
Press Enter to accept the default path `/home/<you>/.ssh/id_ed25519`. Use a passphrase for extra safety.
## Add the public key to Gitea
```bash
cat ~/.ssh/id_ed25519.pub
```
Copy the full output, then open `http://git.klud.top/user/settings/keys` in your browser and paste it. Title: `linux-<yourname>`.
## Accept the server fingerprint and test
```bash
ssh -T git@thunderobot -p 222
```
- If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
- Expected output: `Hi there, <yourname>! You've successfully authenticated with the key named linux-<yourname>, but Gitea does not provide shell access.`
## Clone a repo
```bash
git clone git@thunderobot:222/danchie/tekton.git
```
Or with tea:
```bash
tea repos clone --git-protocol ssh danchie/tekton
```
## Troubleshooting
- **`Permission denied (publickey)`** — Your key wasn't added in the Gitea UI, or the agent hasn't loaded it. Run `ssh-add ~/.ssh/id_ed25519`.
- **`Host key verification failed`** — Run the `ssh -T` command above interactively at least once.
- **`ssh: connect to host thunderobot port 222: Connection refused`** — Ensure Tailscale is running and you can reach `100.93.226.13`.
- **`ssh: Could not resolve hostname thunderobot`** — Run `tailscale ping thunderobot` to verify tailnet DNS works. If not, use `ssh -T git@100.93.226.13 -p 222` instead.
+42
View File
@@ -0,0 +1,42 @@
# SSH Setup — Windows
## Install Git for Windows
Download from https://git-scm.com/download/win and install with default options.
This installs `git`, `ssh`, and `git-bash`.
## Generate an SSH key
Open **Git Bash** and run:
```bash
ssh-keygen -t ed25519 -C "your-name@example.com"
```
Press Enter to accept the default path `C:\Users\<you>\.ssh\id_ed25519`. Set a passphrase, or leave it empty.
## Add the public key to Gitea
```bash
cat ~/.ssh/id_ed25519.pub
```
Copy the full output, then open `http://git.klud.top/user/settings/keys` in your browser and paste it. Title: `windows-<yourname>`.
## Accept the server fingerprint and test
```bash
ssh -T git@thunderobot -p 222
```
- If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
- Expected output: `Hi there, <yourname>! You've successfully authenticated with the key named windows-<yourname>, but Gitea does not provide shell access.`
If you get this message, the key is recognized.
## Clone a repo
```bash
git clone git@thunderobot:222/danchie/tekton.git
```
Or with tea:
```bash
tea repos clone --git-protocol ssh danchie/tekton
```
## Troubleshooting
- **`Permission denied (publickey)`** — Your key wasn't added in the Gitea UI, or `~/.ssh/id_ed25519` isn't being offered. Run `ssh-add ~/.ssh/id_ed25519` in Git Bash.
- **`Host key verification failed`** — Run the `ssh -T` command above interactively at least once.
- **`ssh: connect to host thunderobot port 222: Connection refused`** — Ensure you can reach the tailnet host: `ping 100.93.226.13`. If ping fails, your machine isn't on the tailnet.
+35
View File
@@ -0,0 +1,35 @@
# SSH Setup — macOS
## Generate an SSH key
Open **Terminal** and run:
```bash
ssh-keygen -t ed25519 -C "your-name@example.com"
```
Press Enter to accept the default path `/Users/<you>/.ssh/id_ed25519`. Use a passphrase for extra safety.
## Add the public key to Gitea
```bash
cat ~/.ssh/id_ed25519.pub
```
Copy the full output, then open `http://git.klud.top/user/settings/keys` in your browser and paste it. Title: `macos-<yourname>`.
## Accept the server fingerprint and test
```bash
ssh -T git@thunderobot -p 222
```
- If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
- Expected output: `Hi there, <yourname>! You've successfully authenticated with the key named macos-<yourname>, but Gitea does not provide shell access.`
## Clone a repo
```bash
git clone git@thunderobot:222/danchie/tekton.git
```
Or with tea:
```bash
tea repos clone --git-protocol ssh danchie/tekton
```
## Troubleshooting
- **`Permission denied (publickey)`** — Your key wasn't added in the Gitea UI, or the key isn't loaded in the agent. Run `ssh-add ~/.ssh/id_ed25519`.
- **`Host key verification failed`** — Run the `ssh -T` command above interactively at least once.
- **`ssh: connect to host thunderobot port 222: Connection refused`** — Ensure Tailscale is running and you can reach `100.93.226.13`.