docs: update clone instructions for Gitea SSH and HTTPS
+20
-2
@@ -2,6 +2,26 @@
|
||||
|
||||
Developer wiki for the Tekton Dash Armageddon project.
|
||||
|
||||
## Clone
|
||||
|
||||
SSH is preferred:
|
||||
|
||||
```bash
|
||||
git clone git@ssh.git.klud.top:danchie/tekton.git
|
||||
```
|
||||
|
||||
HTTPS also works:
|
||||
|
||||
```bash
|
||||
git clone https://git.klud.top/danchie/tekton.git
|
||||
```
|
||||
|
||||
First-time SSH setup:
|
||||
|
||||
- [Linux](./SSH-Setup-Linux)
|
||||
- [macOS](./SSH-Setup-macOS)
|
||||
- [Windows](./SSH-Setup-Windows)
|
||||
|
||||
## Pages
|
||||
|
||||
- [Skin Creation Workflow](./Skin-Creation-Workflow) — Authoring skin materials and registering them in the catalog.
|
||||
@@ -11,5 +31,3 @@ Developer wiki for the Tekton Dash Armageddon project.
|
||||
- [SSH Setup — Linux](./SSH-Setup-Linux) — Setup SSH key and clone on Linux.
|
||||
- [SSH Setup — macOS](./SSH-Setup-macOS) — Setup SSH key and clone on macOS.
|
||||
- [SSH Setup — Windows](./SSH-Setup-Windows) — Setup SSH key and clone on Windows.
|
||||
|
||||
Cloning requires SSH over Tailscale. HTTPS is disabled on this instance.
|
||||
|
||||
+43
-14
@@ -1,36 +1,65 @@
|
||||
# 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.`
|
||||
Copy the full output, then open:
|
||||
|
||||
## Clone a repo
|
||||
```bash
|
||||
git clone git@thunderobot:222/danchie/tekton.git
|
||||
```text
|
||||
https://git.klud.top/user/settings/keys
|
||||
```
|
||||
|
||||
Paste it as a new SSH key. Title example: `linux-<yourname>`.
|
||||
|
||||
## Test SSH
|
||||
|
||||
```bash
|
||||
ssh -T git@ssh.git.klud.top
|
||||
```
|
||||
|
||||
If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
|
||||
|
||||
Expected output:
|
||||
|
||||
```text
|
||||
Hi there, <yourname>! You've successfully authenticated with the key named linux-<yourname>, but Gitea does not provide shell access.
|
||||
```
|
||||
|
||||
## Clone
|
||||
|
||||
SSH is preferred:
|
||||
|
||||
```bash
|
||||
git clone git@ssh.git.klud.top:danchie/tekton.git
|
||||
```
|
||||
|
||||
HTTPS also works:
|
||||
|
||||
```bash
|
||||
git clone https://git.klud.top/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.
|
||||
|
||||
- **`Permission denied (publickey)`** — Your key was not added in Gitea, or the agent has not loaded it. Run `ssh-add ~/.ssh/id_ed25519`.
|
||||
- **`Host key verification failed`** — Run the `ssh -T` command above interactively once.
|
||||
- **`Could not resolve hostname ssh.git.klud.top`** — DNS cache stale. Wait a few minutes or flush DNS.
|
||||
|
||||
+42
-13
@@ -1,42 +1,71 @@
|
||||
# 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`.
|
||||
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
|
||||
Copy the full output, then open:
|
||||
|
||||
```text
|
||||
https://git.klud.top/user/settings/keys
|
||||
```
|
||||
- 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.
|
||||
Paste it as a new SSH key. Title example: `windows-<yourname>`.
|
||||
|
||||
## Test SSH
|
||||
|
||||
## Clone a repo
|
||||
```bash
|
||||
git clone git@thunderobot:222/danchie/tekton.git
|
||||
ssh -T git@ssh.git.klud.top
|
||||
```
|
||||
|
||||
If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
|
||||
|
||||
Expected output:
|
||||
|
||||
```text
|
||||
Hi there, <yourname>! You've successfully authenticated with the key named windows-<yourname>, but Gitea does not provide shell access.
|
||||
```
|
||||
|
||||
## Clone
|
||||
|
||||
SSH is preferred:
|
||||
|
||||
```bash
|
||||
git clone git@ssh.git.klud.top:danchie/tekton.git
|
||||
```
|
||||
|
||||
HTTPS also works:
|
||||
|
||||
```bash
|
||||
git clone https://git.klud.top/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.
|
||||
|
||||
- **`Permission denied (publickey)`** — Your key was not added in Gitea, or Git Bash is not offering `~/.ssh/id_ed25519`. Run `ssh-add ~/.ssh/id_ed25519`.
|
||||
- **`Host key verification failed`** — Run the `ssh -T` command above interactively once.
|
||||
- **`Could not resolve hostname ssh.git.klud.top`** — DNS cache stale. Wait a few minutes or flush DNS.
|
||||
|
||||
+43
-13
@@ -1,35 +1,65 @@
|
||||
# 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.`
|
||||
Copy the full output, then open:
|
||||
|
||||
## Clone a repo
|
||||
```bash
|
||||
git clone git@thunderobot:222/danchie/tekton.git
|
||||
```text
|
||||
https://git.klud.top/user/settings/keys
|
||||
```
|
||||
|
||||
Paste it as a new SSH key. Title example: `macos-<yourname>`.
|
||||
|
||||
## Test SSH
|
||||
|
||||
```bash
|
||||
ssh -T git@ssh.git.klud.top
|
||||
```
|
||||
|
||||
If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
|
||||
|
||||
Expected output:
|
||||
|
||||
```text
|
||||
Hi there, <yourname>! You've successfully authenticated with the key named macos-<yourname>, but Gitea does not provide shell access.
|
||||
```
|
||||
|
||||
## Clone
|
||||
|
||||
SSH is preferred:
|
||||
|
||||
```bash
|
||||
git clone git@ssh.git.klud.top:danchie/tekton.git
|
||||
```
|
||||
|
||||
HTTPS also works:
|
||||
|
||||
```bash
|
||||
git clone https://git.klud.top/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`.
|
||||
|
||||
- **`Permission denied (publickey)`** — Your key was not added in Gitea, or the agent has not loaded it. Run `ssh-add ~/.ssh/id_ed25519`.
|
||||
- **`Host key verification failed`** — Run the `ssh -T` command above interactively once.
|
||||
- **`Could not resolve hostname ssh.git.klud.top`** — DNS cache stale. Wait a few minutes or flush DNS.
|
||||
|
||||
Reference in New Issue
Block a user