Help Center← Back to Dashboard
Getting Started
What is Aithroyz?Quickstart: First EnvironmentCloud CredentialsPlans & Approvals
Environments
OverviewLifecycle PhasesTTL Auto-DestroyExtending TTLDestroying an Environment
Tools Reference
OverviewElastic Stack (SIEM)Wazuh (XDR)MITRE CalderaTheHive & DFIR-IRISVelociraptorOpenCTIGrafana + PrometheusShuffle SOARn8nUptime KumaLLM GatewayOpen WebUIFlowiseOpenClawOllamaQdrantLangfusePortainerGiteaSonarQubeCode ServerMattermostMinIOMetabaseHashiCorp VaultKeycloak SSONetBoxLocalStack
Access & Security
Google SSOTenant IsolationPasskeys & MFATeam Members
API & Integrations
API KeysMCP Tools (Clevername)Terraform ExportWebhooks & Callbacks
Stack Presets
SOC PlatformIR / DFIR LabThreat HuntingQuick Sandbox
Settings
Cloud KeysAPI KeysBillingAudit Log
Troubleshooting
Common IssuesDeployment FailuresDNS & ConnectivityTool Health Checks
Aithroyz Help
Help CenterTools ReferenceGitea (Self-hosted Git)

Gitea (Self-hosted Git)

Gitea is a lightweight, self-hosted Git service — repositories, pull requests, issues, code review, Gitea Actions (CI/CD), and package registry.

Aithroyz deploys Gitea with Google SSO integrated when the google-oidc module is included. The first account to register becomes the site admin.

Access

URL: https://gitea.<env-name>.ops.aithroyz.com
Admin account: The first user to register is automatically promoted to site admin.

Creating a repository

1. New repository
Click the + icon in the top-right → New Repository. Give it a name and optional description.
2. Initialize with README
Check Initialize this repository — this creates a default branch so you can clone immediately.
3. Clone
Copy the HTTPS or SSH clone URL from the repository page and run git clone.
git clone https://gitea.<env-name>.ops.aithroyz.com/<username>/<repo>.git

SSH keys

Add your public key to Gitea to clone and push without a password.

# Generate a key (skip if you already have one)
ssh-keygen -t ed25519 -C "your@email.com"

# Copy the public key
cat ~/.ssh/id_ed25519.pub

Paste the output into User Settings → SSH / GPG Keys → Add Key. Then clone via SSH:

git clone git@gitea.<env-name>.ops.aithroyz.com:<username>/<repo>.git

Gitea Actions CI/CD

Gitea Actions is compatible with GitHub Actions syntax. Create a workflow file in your repo:

# .gitea/workflows/ci.yml
name: CI

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run tests
        run: |
          npm install
          npm test

Register a runner using the act binary:

# Download act runner from Gitea releases, then register:
./act_runner register \
  --instance https://gitea.<env-name>.ops.aithroyz.com \
  --token <runner-token-from-gitea-admin>
ℹ
Find the runner registration token under Site Administration → Runners → Create Runner.

Webhooks for n8n

Trigger n8n workflows automatically when code is pushed to a repository.

1. Open repo Settings
In your repository, go to Settings → Webhooks → Add Webhook → Gitea.
2. Set the target URL
Paste the n8n Production Webhook URL (e.g. https://n8n.<env-name>.ops.aithroyz.com/webhook/your-path).
3. Choose events
Select Push Events, or choose specific events like Pull Request and Issue Comment.
4. Add and test
Click Add Webhook, then use the Test Delivery button to verify n8n receives the payload.

Tips

✓
Use Gitea as the source of truth for n8n workflow JSONs and Flowise flow exports — commit them to a repo for version history and easy restore.
✓
Add a SonarQube webhook on pull request events to automatically trigger a code quality scan before merging.
Related Articles
SonarQube (Code Quality)Read article →n8n (Workflow Automation)Read article →