Automation — n8n, Forgejo Actions runner
Find a file
2026-03-22 06:31:29 +00:00
.forgejo/workflows ci: add Coolify sync workflow for automation-stack 2026-03-20 22:15:25 +00:00
.gitea/issue_template chore: add infrastructure change issue template 2026-03-04 13:47:48 +00:00
.env.example Add .env.example 2026-03-04 01:19:02 +00:00
CLAUDE.md Fix CLAUDE.md encoding (was double base64-encoded) 2026-03-06 08:31:58 +00:00
docker-compose.yml chore: bump n8n 2.8.3 -> 2.13.2 (INF-9) 2026-03-21 19:28:45 +00:00
README.md docs: update README for Scheme B rename (g1-automation → svc-automation) 2026-03-22 06:31:29 +00:00

svc-automation

Workflow automation and CI/CD execution for Generate One — n8n workflows and the Forgejo Actions runner.

Status License Platform Domain


Overview

svc-automation connects platform events (git pushes, webhooks, scheduled tasks) to automated responses. n8n provides a visual workflow engine for building multi-step automations triggered by Forgejo webhooks, schedules, and external events. The Forgejo Actions runner (au2404-runner) executes CI/CD pipelines defined in .forgejo/workflows/*.yml across all Generate One repos.

🏗️ Architecture

graph TD
    A[Forgejo<br/>git.generate.one] -->|push webhook| B[n8n<br/>n8n.generate.one]
    A -->|workflow dispatch| C[Forgejo Actions Runner<br/>au2404-runner<br/>host-level service]
    B -->|workflow: summarize| D[LiteLLM<br/>g1-llm-mini]
    B --> E[PostgreSQL<br/>svc-infra n8n DB]
    C -->|executes .forgejo/workflows/| F[deploy.yml<br/>deploy-knowledge.yml<br/>etc.]
    F -->|Coolify API| G[Coolify<br/>app.coolify.io]

📦 Services

Service Image Port Description
n8n docker.n8n.io/n8nio/n8n:latest 5678 Visual workflow automation platform

Note: The Forgejo Actions runner (v6.3.1) runs as a host-level systemd service — not in this compose file. It shares the Docker socket to execute container-based CI steps.

Domain: n8n.generate.one Coolify Service UUID: vkog4ckwo8408kgsgkcc8gso Coolify Project: svc-automation

🚀 Quick Start

# Service directory
cd /data/coolify/services/vkog4ckwo8408kgsgkcc8gso

# Apply changes (use local deploy — external volume)
docker compose up -d

# View logs
docker compose logs -f n8n

# Check health
curl -s https://n8n.generate.one/healthz

Important: Use local deploy pattern (docker compose up -d), NOT Coolify UI deploy. The n8n data volume is external — Coolify deploy mangles external volume names and would destroy workflow data.

🔧 Configuration

Variable Description Default
RESOURCE_UUID Coolify resource UUID for container naming vkog4ckwo8408kgsgkcc8gso
POSTGRES_HOST PostgreSQL host (svc-infra container) postgres-u8kg4sscgccccok088048so4
POSTGRES_PASSWORD PostgreSQL password for n8n database
N8N_ENCRYPTION_KEY Encryption key for credentials storage

Internal DB connection: postgresql://n8n:{PASSWORD}@postgres-u8kg4sscgccccok088048so4:5432/n8n

🤖 Active Workflows

Workflow Trigger Description
Forgejo-Push-Summarizer Webhook (git push) Summarizes commits using g1-llm-mini on each push event

🔄 Forgejo Actions Runner

The Actions runner (au2404-runner) executes workflows in these repos:

Repo Workflow Trigger
g1-brain deploy-knowledge.yml Push to main
g1-brain deploy-memory.yml Push to main
g1-project deploy.yml Push to main

Each workflow calls the Coolify API to trigger a service redeploy, keeping Forgejo as the single source of truth for compose files (Rule 62).

🔗 Dependencies

Depends on:

  • svc-infra — PostgreSQL database (n8n DB)
  • g1-llm — LiteLLM for workflow AI steps (push summarizer)

Depended on by:

  • g1-git — Forgejo push events trigger n8n webhooks
  • All repos — Forgejo Actions runner executes CI/CD workflows
Repo Relationship
g1-core PostgreSQL backend
g1-git Forgejo triggers webhooks to n8n
g1-brain Forgejo Actions deploy workflows
g1-project Forgejo Actions deploy workflow
g1-shared Shared conventions for CI/CD workflows

🛡️ Part of Generate One

Generate One — AI infrastructure that answers to you.

Self-hosted, sovereign AI platform. generate.one