docs: repoint forge references from Codeberg to git.dev.egbt.com
The origin moved to the private Forgejo instance at git.dev.egbt.com (egbt/secrets). Git history, all 16 branches, 13 tags, and all 13 releases were migrated with identical SHAs and release bodies. - CLAUDE.md: replace the "Codeberg operations" section with "Forge operations", switching tea invocations to `--login egbt --repo egbt/secrets`. Records three things that are easy to get wrong: Forgejo's SSH listens on port 2222 (port 22 is the host's own sshd, so a bare git@host:path fails with "Permission denied (publickey)"); the host is Tailscale-only, so off-VPN failures are connectivity, not credentials; and the stale `codeberg` tea login is still configured and can be silently fallen back to in non-interactive mode. - CLAUDE.md: note the instance has an Actions runner available, though no workflow is configured yet — local bats remains the merge gate. - README.md: clone URLs now point at the new host. - CHANGELOG.md: release links now point at the new host. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BrUoYuUMoTj91rzV4vxGPB
This commit is contained in:
parent
c83935a92f
commit
d984e2abc7
3 changed files with 30 additions and 18 deletions
|
|
@ -69,7 +69,7 @@ two commands to finish setup. It never edits your shell config and never runs
|
|||
sudo — it prints the commands so you stay in control.
|
||||
|
||||
```bash
|
||||
git clone https://codeberg.org/egbt/secrets.git ~/dev/secrets
|
||||
git clone https://git.dev.egbt.com/egbt/secrets.git ~/dev/secrets
|
||||
cd ~/dev/secrets
|
||||
./install.sh
|
||||
```
|
||||
|
|
@ -82,7 +82,7 @@ this machine with one of the two flows below.
|
|||
|
||||
```bash
|
||||
# 1. Create a PRIVATE repo for your encrypted secrets (github.com/new or a
|
||||
# Codeberg/GitLab private repo). It holds only ciphertext — never your key.
|
||||
# GitLab/Forgejo private repo). It holds only ciphertext — never your key.
|
||||
# Then wire it up and push the store in one command:
|
||||
secrets init --remote git@github.com:<you>/my-secrets.git
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ On a second machine, a desktop, or a teammate's laptop:
|
|||
|
||||
```bash
|
||||
# 1. Clone the tool and run the bootstrap (as in Setup above)
|
||||
git clone https://codeberg.org/egbt/secrets.git ~/dev/secrets
|
||||
git clone https://git.dev.egbt.com/egbt/secrets.git ~/dev/secrets
|
||||
cd ~/dev/secrets && ./install.sh # add the printed PATH line to your shell config
|
||||
|
||||
# 2. Get key.txt onto this machine (the one manual, out-of-band step):
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue