To connect GitHub to Coolify, create a GitHub App source in Coolify, give it a publicly reachable Coolify base URL, register the app with GitHub, install it for the repositories you want, and create a Coolify application from that source. Applications created this way use Deploy on push (webhooks) by default, so a push to the configured branch can start a deployment automatically.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
The two details that cause most failed setups are easy to miss: GitHub must be able to reach the endpoint over the internet, and Coolify expects the base URL only, such as https://coolify.example.com, not a URL ending in /webhooks.
As an Amazon Associate I earn from qualifying purchases.
What the Coolify GitHub App connection does
A GitHub App gives Coolify authenticated access to repositories without storing a personal GitHub password. During registration, Coolify generates and stores the app ID, client credentials, webhook secret and private key it needs to authenticate with GitHub and receive repository events.
You choose the installation scope in GitHub. The app can be installed for every repository in a personal account or organization, or only for selected repositories. That scope controls which repositories Coolify can list and clone; it does not automatically grant access to repositories that were left out of the installation.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
The integration also receives provider events for Coolify. That means an application created with the GitHub App normally does not require you to copy a separate manual webhook URL into every repository. Push and pull-request events can be used for production deployments and preview environments when the required permissions are enabled.
Before you start
- A running Coolify instance with a stable public base URL.
- Administrative access to the GitHub personal account or organization where the app will be registered and installed.
- The repository must be reachable by the GitHub App installation you create.
- DNS and TLS for the Coolify URL should already work from the public internet. GitHub has to deliver webhook requests to that address.
- A deployment server selected in the Coolify project and environment.
- The branch, build method, domain and environment variables you plan to use for the application.
If Coolify is only available on a private network, behind a firewall that blocks inbound requests, or at a hostname that GitHub cannot resolve, automatic events will not arrive. Make the endpoint reachable before troubleshooting repository permissions or build settings.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Create a GitHub App source in Coolify
- Open Sources. In the Coolify dashboard, open Sources and choose New source > GitHub App.
- Name the source. Enter a descriptive source name. If the app belongs to an organization, optionally enter the GitHub organization as part of the source configuration.
- Select the GitHub.com installation method. For GitHub.com, choose Automated installation. This is the shortest setup because Coolify can pass the generated credentials, callback information and webhook configuration through the registration flow.
- Enter the webhook endpoint. Use the public Coolify base URL, for example
https://coolify.example.com. Do not append/webhooks. The endpoint value is the base address that GitHub uses to reach the Coolify integration. - Set preview permissions if needed. If pull-request preview deployments are part of your workflow, set Preview deployment access to Read and update pull requests. The integration also needs read access to repository contents, repository metadata and email addresses.
- Register the app. Select Register with GitHub. GitHub asks for a unique GitHub App name; enter one that is not already used in the relevant account or organization, then choose Create GitHub App.
After registration, Coolify stores the generated App ID, client credentials, webhook secret and private key. Treat those values as credentials: do not paste them into source files, commit them to a repository or share them in an issue.
Install the app for the right repositories
- When GitHub shows the repository-access prompt, choose All repositories or Only select repositories.
- With Only select repositories, add each repository that Coolify must clone or monitor.
- Select Install to complete the installation.
Selecting only the repositories required by your deployments limits account-wide access. It also means a newly created repository will not appear in Coolify until you edit the GitHub App installation and add it.
If an existing Coolify application suddenly cannot clone a repository or stops receiving new deployments, check the GitHub App installation first. Removing a repository from the installation prevents new clones and webhook deployments for applications that use that source.
Create a Coolify application from the private repository
- In Coolify, open the target Project and Environment.
- Select + New, then choose Private Repository (with GitHub App).
- Select the deployment server and the GitHub App source you just created.
- Choose the repository from the list and select Load Repository.
- Choose the branch to deploy. This is the branch whose pushes will update this application unless you configure a preview deployment or another application for other branches.
- Choose the build settings appropriate to the repository, then configure the application domain and environment variables.
- Deploy the application and wait for the first deployment to finish.
Loading a repository successfully proves that Coolify can use the app credentials and installation scope. It does not by itself prove that webhook delivery or automatic deployment is working; verify those separately with a test push.
Recommended Free Tools
Rank #2
- [15W Ryzen 7 Agentic PC for Everyday Workflows] Powered by the AMD Ryzen 7 7730U processor (8 Cores, 16 Threads), the GEEKOM A5 is built for sustained productivity. It doubles as your cloud-native Agentic AI assistant, seamlessly hosting cloud AI tasks, automating office workflows, and handling intelligent document summarization without complex local deployment. Smoothly manage Microsoft Office, dozens of browser tabs, heavy Excel spreadsheets, and remote learning throughout your workday.
- [Smart Value Now, Expandable for Tomorrow] Equipped with 16GB RAM and a fast 256GB PCIe NVMe SSD for snappy daily performance, the A5 offers incredible value. Need more space later? It features dual-slot DDR4 RAM (upgradable to 64GB) and supports an M.2 SSD up to 4TB. With an extra M.2 2242 slot and 2.5" HDD bay for up to 10TB total storage, you get the flexibility to scale your storage seamlessly as your needs grow, beating soldered LPDDR solutions.
- [Multi-Display Connectivity for Maximum Productivity] Create a complete workstation with support for up to four displays through Dual HDMI and Dual USB-C ports, including up to 8K output via USB-C. Stay connected with Wi-Fi 6, Bluetooth 5.4, a 2.5GbE LAN port, SD card reader, and multiple USB ports for fast networking, efficient multitasking, and seamless connectivity across all your devices.
- [Built to Stay Cool, Quiet & Reliable] More than fast, the GEEKOM A5 is built to last. A reinforced one-piece all-metal internal frame enhances structural strength, while the upgraded IceBlast 3.0 cooling system improves cooling efficiency by up to 42% with up to 35% greater airflow for quieter operation. Backed by 339 reliability tests and a 72-hour full-load aging test, it's engineered for dependable long-term performance.
- 🏢[Business-Ready, Compact & Efficient] Pre-installed OS, the GEEKOM A5 supports Wake-on-LAN, Scheduled Power On, and Group Policy, making deployment and remote management simple for businesses. Its ultra-compact 0.6L design fits neatly behind monitors or into space-limited workstations while delivering excellent power efficiency for home offices, front desks, and commercial environments.
Turn on and verify automatic deployments
Applications created through a GitHub App normally have Auto deploy set to Deploy on push (webhooks). Confirm the setting before relying on it:
- Open the application in Coolify.
- Go to Advanced > Deployment.
- Set Auto deploy to Deploy on push (webhooks) if it is set to manual.
- Push a commit to the application’s configured branch.
- Open Deployment Logs and confirm that a webhook deployment appears for that commit.
A push to a different branch does not update the production application unless that branch is configured for a preview deployment or is connected to another application. A successful Git push is therefore not evidence that production should have changed; the branch mapping in Coolify determines which application receives the event.
Configure pull-request previews
Pull-request previews require more than push deployment. In the GitHub App source, set Preview deployment access to Read and update pull requests, and retain read access to repository contents, metadata and email addresses. These permissions let Coolify read the code needed to build the preview and update the pull request with the preview state or address.
Install the app on the repository that will open the pull request. If the repository is not included in the installation scope, Coolify cannot receive or act on its pull-request events even when the source itself is configured correctly.
Use Watch Paths in a monorepo
In a monorepo, every push can contain changes unrelated to a particular application. Coolify’s Watch Paths setting lets an application react only when changed files match configured patterns. Open General > Build and add one pattern per line.
The pattern syntax supports *, **, ? and negation with !. The last matching pattern wins. For example:
Rank #3
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
apps/api/**
packages/shared/**
!apps/api/**/*.mdThis example watches the API and shared package trees but excludes Markdown-only changes under the API directory. A change to apps/api/server.js matches the first rule and can trigger a deployment; a change to apps/api/README.md is excluded by the later negated rule.
Watch Paths filter provider webhook events that include changed-file information. They do not block a manual deployment from the Coolify dashboard or an authenticated call to a Deploy Webhook. Test the patterns with a documentation-only commit before depending on them in production, then inspect the deployment log to verify that the expected application was skipped or started.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why a push did not trigger a deployment
The endpoint is not reachable from GitHub
GitHub must reach the webhook endpoint from the internet. Check DNS resolution, firewall rules, reverse-proxy routing and TLS. In Coolify, confirm that the source uses the base URL, such as https://coolify.example.com, rather than https://coolify.example.com/webhooks. A private-only hostname or an inbound firewall block prevents delivery regardless of repository permissions.
The app is not installed on that repository
Open the GitHub App installation settings and verify that the repository is included. This is especially important after moving a repository, recreating an installation or choosing Only select repositories. If access was removed, restore it and then retry the repository load or test push.
Auto deploy is set to manual
Go to Advanced > Deployment and inspect Auto deploy. Choose Deploy on push (webhooks). Changing the setting does not deploy an old commit automatically; push a new commit to test it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThe push went to the wrong branch
Compare the branch in the GitHub push with the branch configured for the Coolify application. A push to a feature or development branch will not update production unless you created a preview deployment or a separate application for that branch.
Rank #4
- This Certified Refurbished product is tested and certified to look and work like new. The refurbishing process includes functionality testing, basic cleaning, inspection, and repackaging. The product ships with all relevant accessories, a minimum 90-day warranty, and may arrive in a generic box. Only select sellers who maintain a high-performance bar may offer Certified Refurbished products on Amazon.com.
- Dell OptiPlex 7050 Micro Computer, Intel Quad Core i5-6500T up to 3.1GHz, 16G DDR4, 256G SSD.
- Includes: USB Keyboard & Mouse, Microsoft office 30 days free trail.
- Ports: 1 x RJ-45, 1 x HDMI, 1 x DP, 6 x USB 3.0.
- 4K Support: Support 4K (3840x2160) Dual display, makes it easy to connect two monitors at the same time, and you can expand working Windows, mirror content, or expand a single window across multiple monitors.
Watch Paths filtered the change
Review General > Build > Watch Paths. In a monorepo, a valid webhook can be intentionally ignored when none of the changed files match the final pattern result. Temporarily test with a file that should match, or simplify the rules until the match behavior is clear.
You checked only GitHub, not Coolify
Use both sides of the event chain. In Coolify, inspect Deployment Logs for a deployment associated with the commit. In GitHub, inspect the repository’s webhook delivery status for the event response. A push that appears in GitHub but has no Coolify delivery points to endpoint or integration trouble; a delivery that reaches Coolify but produces no deployment usually points to branch, auto-deploy or Watch Path configuration.
Deploy keys and manual webhooks as fallbacks
A GitHub App is usually the most integrated choice when you need selected repositories, pull-request events or several applications. A deploy key is a narrower alternative: one SSH key grants access to one private repository and should normally be read-only. The key authenticates repository access only; it does not create automatic deployment triggers. You still need a repository webhook or an external workflow to tell Coolify when to deploy.
For an application using a public repository URL or a deploy key, create a manual Git webhook in Coolify. Copy the generated GitHub URL and secret, then add them under GitHub repository Settings > Webhooks. Select the push event, keep SSL verification enabled and set Coolify’s auto-deploy mode to Deploy on push (webhooks). The webhook secret must match on both sides and contain at least 16 characters.
Manual webhooks separate two responsibilities that the GitHub App combines: the repository credential used to fetch code and the webhook credential used to start a deployment. This can be useful when an app cannot be installed, but it gives you more configuration to maintain.
Which connection method fits your repository?
| Method | Repository privacy | Access scope | Pull-request previews | Webhook setup | Where builds run |
|---|---|---|---|---|---|
| Public repository over HTTPS | Public | Public code; no private repository credential required | Not provided by the repository URL alone | Manual webhook needed for push-triggered deployments | Coolify |
| Deploy key | Private repository | One repository per SSH key; normally read-only | Not integrated by the key itself | Manual webhook or external workflow required | Coolify |
| GitHub App | Selected public or private repositories | One, selected or all repositories, depending on installation | Supported when pull-request permissions are enabled | Integrated provider events; no manual URL copy for the normal setup | Coolify |
| GitHub Actions handoff | Repositories accessible to GitHub Actions | Controlled by the workflow and repository permissions | Handled by the workflow rather than Coolify’s GitHub App integration | Workflow invokes Coolify after its own checks | GitHub Actions builds and publishes the image; Coolify deploys it |
Choose a GitHub App when you want Coolify to select private repositories, receive integrated push and pull-request events and manage several repository installations. Use a deploy key when one private repository needs simple read access and you are comfortable configuring its trigger separately. Use the GitHub Actions route when tests or image builds must complete in GitHub before Coolify receives a deployable image.
A repeatable verification checklist
- The Coolify source is a GitHub App using Automated installation for GitHub.com.
- The endpoint is a public HTTPS base URL with no
/webhookssuffix. - The app is installed for the exact repository that the Coolify application uses.
- The application was loaded through Private Repository (with GitHub App).
- The configured branch matches the branch receiving the test commit.
- Advanced > Deployment > Auto deploy is set to Deploy on push (webhooks).
- Preview deployments have Read and update pull requests plus read access to contents, metadata and email addresses.
- Watch Paths, if present, match the files changed by the test commit.
- Coolify Deployment Logs show the commit and deployment trigger.
- GitHub webhook delivery status confirms that GitHub reached the endpoint.
Security and maintenance considerations
Repository installation scope is your main access-control decision. Only select repositories limits what the app can list and clone, while All repositories is simpler for an organization that expects to deploy many repositories. Review the installation after repository transfers, ownership changes or access-policy updates.
Keep the app’s private key, client credentials and webhook secret protected. If credentials are regenerated or the app is recreated in GitHub, update the corresponding Coolify source rather than leaving two partially configured integrations active. Retest both repository loading and a push-triggered deployment after any credential, hostname, reverse-proxy or firewall change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
