ci-cd-setup

Connect Gitea repositories to Coolify with deploy keys and webhooks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bullish0x/paas-ai-stack --skill ci-cd-setup-bullish0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-setup
Source: https://github.com/bullish0x/paas-ai-stack/tree/main/skills/ci-cd
Command: npx skills add https://github.com/bullish0x/paas-ai-stack --skill ci-cd-setup-bullish0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Setting up CI/CD pipelines between Gitea and Coolify is manual and error-prone; this skill automates the end-to-end process.

Core Features & Use Cases

  • Official Coolify integration: uses deploy keys and webhooks to connect repositories to Coolify for automated builds and deployments.
  • Automated provisioning: creates deploy keys, configures webhooks, and registers apps in Coolify to enable seamless deployment workflows.
  • Flexible deployment scenarios: supports multiple repos and environments, enabling production and staging deployments via webhook-driven triggers.

Quick Start

Execute the setup-ci-cd.sh script with the repo name, subdomain, and optional port to bootstrap CI/CD for your app.

Frequently Asked Questions about ci-cd-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Gitea to Coolify deployments with webhooks and deploy keys?

You can automate Gitea to Coolify deployments by using deploy keys and webhooks to connect your repositories, which registers apps in Coolify and enables seamless, automated build and deployment workflows triggered by code pushes.

What environment variables are required to set up CI/CD between Gitea and Coolify?

Setting up CI/CD between Gitea and Coolify requires GITEA_TOKEN and COOLIFY_TOKEN environment variables to authenticate API requests and automate the provisioning of deploy keys, webhooks, and app registrations.

Can I configure multiple staging and production environments for a single Gitea repository in Coolify?

Yes, the setup supports flexible deployment scenarios across multiple repositories and environments, enabling you to configure both production and staging deployments in Coolify via webhook-driven triggers from Gitea.

What is the best way to bootstrap an automated CI/CD pipeline for a Gitea repository in Coolify?

The best way to bootstrap an automated CI/CD pipeline is to execute the setup script with your repository name, subdomain, and an optional port, which automatically provisions the deploy keys and webhooks needed for Coolify integration.

Does setting up Coolify integration with Gitea require manual webhook configuration?

No, the process automates the end-to-end creation of deploy keys and the configuration of webhooks, eliminating the manual and error-prone steps typically required to connect Gitea repositories to Coolify for deployments.