Forgejo & Git Hosting

Tawa provides private Git hosting via Forgejo at git.insureco.io. Push to deploy — no CI config needed.

Getting Started

tawa login authenticates both Bio-ID and Forgejo in a single flow:

tawa login

Create a repository with an auto-deploy webhook:

tawa git create my-service

Then add the remote and push:

git remote add origin [email protected]:username/my-service.git
git push -u origin main

That first push triggers the builder automatically — your service will be built, deployed, and live within minutes.

Auto-Deploy Webhooks

When you create a repo with tawa git create, the CLI registers a webhook on Forgejo that notifies the builder on every push to the default branch:

1. You push to main (or master)
2. Forgejo sends a webhook payload to the builder with the commit SHA
3. The builder clones at that exact commit and runs the full deploy pipeline
4. Your service is built, pushed, deployed via Helm, DNS configured

NOTE: The webhook only fires on pushes to the default branch. Pushes to feature branches do not trigger a deploy.

Authentication

CI/Headless Environments

1. Go to git.insureco.io → Settings → Applications → Generate New Token
2. Grant Contents: Read-only access to your repos
3. Store the token:

tawa git login <token>

Or set the FORGEJO_TOKEN environment variable for CI systems.

Forgejo vs GitHub

TIP: If you want push-to-deploy without configuring CI, Forgejo is the simplest path. If your team already uses GitHub, use tawa link to connect the repo and deploy manually with tawa deploy.

Common Commands