Other Git Providers

This guide will show you how to use other Git provider with Coolify, such as Gogs, Forgejo, and any other Git-compatible platform.

Public Repositories

You can use public repositories from any Git provider without any additional setup.

Select the Public repository option in Coolify when you create a new resource.
Add your repository URL to the input field, for example: https://git.example.com/username/repository

Caution

You can only use the HTTPS URL.

That's it! Coolify will automatically pull the latest version of your repository and deploy it.

Private Repositories

Private repositories require deploy keys for authentication.

With Deploy Keys

Add a private key (aka Deploy Keys) to Coolify and to your Git repository in the repository settings (usually under Settings / Deploy Keys or SSH Keys).

Caution

You can generate a new key pair with the following command:

ssh-keygen -t ed25519 -C "coolify_deploy_key"

Or you can also use Coolify to generate a new key for you in the Keys & Tokens menu.

Create a new resource and select the Private Repository (with deploy key)
Add your repository URL to the input field, for example: [email protected]:username/repository.git

Caution

You need to use the SSH URL, so the one that starts with git@.

That's it! Coolify will automatically pull the latest version of your repository and deploy it.

Automatic commit deployments (Optional)

For Git providers without direct integration, automatic deployments require triggering the deployment via the Deploy Webhook endpoint.

Caution

This requires your Git provider to support workflow automation or webhook actions (similar to GitHub Actions).

If your provider doesn't support this, you'll need to trigger deployments manually through the Coolify dashboard.

Prerequisites

Create a Coolify API Token in your Coolify dashboard
Get the Deploy Webhook URL from your resource (Your resource → Webhooks menu → Deploy Webhook)

Setup with Workflow/CI System

If your Git provider supports workflow automation (like GitHub Actions, GitLab CI, Forgejo Actions, etc.), you can trigger deployments automatically:

Add your Coolify API token to your repository secrets (e.g., COOLIFY_TOKEN)
Add the Deploy Webhook URL to your repository secrets (e.g., COOLIFY_WEBHOOK)
Create a workflow file that triggers on push events:

# Example workflow (syntax varies by provider)
on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger Coolify Deployment
        run: |
          curl --request GET "${{ secrets.COOLIFY_WEBHOOK }}" \
            --header "Authorization: Bearer ${{ secrets.COOLIFY_TOKEN }}"

That's it! Now when you push to your repository, the workflow will trigger and send a request to Coolify to start a new deployment.

Alternative: Direct Webhooks

Some Git providers allow webhooks to send custom headers. If supported, you can configure a webhook to send a GET request with the Authorization: Bearer YOUR_TOKEN header directly to the Deploy Webhook URL, without needing a workflow file.

Supported Git Providers

This method works with any Git provider that supports standard Git protocols, including:

Gogs
Forgejo
Self-hosted GitLab CE/EE instances
Custom Git servers (gitolite, etc.)
Any Git-over-SSH compatible platform

Comparison with App Integration

Feature	Other Providers	GitHub, GitLab, Bitbucket, Gitea
Repository access	✅ Yes	✅ Yes
Manual deployments	✅ Yes	✅ Yes
Auto-deploy	⚠️ Requires workflow setup	✅ Automatic
Pull request previews	❌ No	✅ Yes

On this page