nest/k3s
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Cleanup AI junk

Browse source
This commit is contained in:
KnightArtorias 2026-07-23 18:39:10 -04:00
parent 9b2c6301ee
commit 228e82cc43
2 changed files with 21 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
IdentityFile ~/.ssh/your-key
View file

@ -1,22 +0,0 @@
## Package Registry
Forgejo includes a package registry for sharing binaries, Docker images, and other artifacts:
- **Docker:** `docker pull weaver.mynest.love/nest/your-image:tag`
- **npm/go/python:** Configure your package manager to authenticate with your Forgejo token (generate one under **Settings → Applications → Generate Token**).
## Tips
- **Two-factor auth:** While passkeys handle SSO, enable 2FA in Forgejo settings for an extra layer of security on the git server itself.
- **Actions:** Use `.forgejo/workflows/` in your repo to define CI pipelines (compatible with GitHub Actions syntax).
- **Webhooks:** Set up webhooks to trigger external services when you push code.
## Related Services
- [Semaphore](https://semaphore.k3s.home.nest) — Ansible automation UI for infrastructure management
- [Keycloak](../technical/security-and-identity.md) — Powers SSO and group-based access control
---
*TODO: Add screenshot of Forgejo repository view with a sample project.*

21
documentation/user-facing/productivity-and-creation/forgejo.md
View file

@ -36,3 +36,24 @@ HTTP Git is disabled for security — use SSH only. Add your public key to your
Example `~/.ssh/config` entry:
## Package Registry
Forgejo includes a package registry for sharing binaries, Docker images, and other artifacts:
- **Docker:** `docker pull weaver.mynest.love/nest/your-image:tag`
- **npm/go/python:** Configure your package manager to authenticate with your Forgejo token (generate one under **Settings → Applications → Generate Token**).
## Tips
- **Two-factor auth:** While passkeys handle SSO, enable 2FA in Forgejo settings for an extra layer of security on the git server itself.
- **Actions:** Use `.forgejo/workflows/` in your repo to define CI pipelines (compatible with GitHub Actions syntax).
- **Webhooks:** Set up webhooks to trigger external services when you push code.
## Related Services
- [Semaphore](https://semaphore.k3s.home.nest) — Ansible automation UI for infrastructure management
- [Keycloak](../technical/security-and-identity.md) — Powers SSO and group-based access control
---
*TODO: Add screenshot of Forgejo repository view with a sample project.*