43 lines
1.1 KiB
Markdown
43 lines
1.1 KiB
Markdown
# OpenClaw Gitea bootstrap
|
|
=======================
|
|
|
|
Created user
|
|
- username: openclaw
|
|
- fullname: OpenClaw
|
|
- email: openclaw@git.an2.io
|
|
|
|
SSH key
|
|
- private key: /home/user/.ssh/id_gitea_openclaw
|
|
- public key: /home/user/.ssh/id_gitea_openclaw.pub
|
|
- Gitea key title: openclaw@xeon
|
|
|
|
SSH config
|
|
- host alias: gitea
|
|
- hostname: git.an2.io
|
|
- port: 222
|
|
- user: git
|
|
- identity: /home/user/.ssh/id_gitea_openclaw
|
|
|
|
Verified
|
|
- ssh -T gitea
|
|
- result: authenticated successfully as openclaw
|
|
|
|
Access token
|
|
- created for user: openclaw
|
|
- token name: openclaw-bootstrap
|
|
- scopes: all
|
|
- token value was generated during bootstrap and should be stored securely if you want API repo management later
|
|
|
|
Recommended usage
|
|
- clone/pull/push via SSH
|
|
- repo create/delete via Gitea API token
|
|
|
|
Example remote forms
|
|
- ssh://git@git.an2.io:222/openclaw/repo.git
|
|
- gitea:openclaw/repo.git (via SSH config alias if your git tooling uses it explicitly)
|
|
|
|
Suggested next steps
|
|
1. Store the generated Gitea token somewhere safe for future API use
|
|
2. Create a first test repo under openclaw
|
|
3. Verify clone, commit, and push with the SSH identity
|