What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Connect Coolify to a GitHub App when you want a private or public repository to deploy automatically after a push. In Coolify, create a GitHub App source, give it access to the required repositories, create an application from that source, and set Auto deploy to Deploy on push (webhooks). GitHub must be able to reach Coolify at a publicly accessible base URL, entered without a /webhooks suffix.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
What the GitHub App integration does
A GitHub App is Coolify’s integrated connection to GitHub. It can grant access to one repository, selected repositories, or every repository in a personal account or organization. The integration supplies repository authentication and provider events, so applications created from it can receive push and pull-request activity without a separately copied Git webhook URL.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The connection has two distinct jobs:
- Repository access: the app installation determines which repositories Coolify can list and clone.
- Deployment events: the webhook endpoint and Coolify’s auto-deploy setting determine whether a qualifying push starts a deployment.
Both jobs must be working. A successful repository clone does not prove that webhook delivery is configured, and a delivered webhook cannot deploy a repository that the app installation no longer includes.
Before you begin
Prepare these items before opening the setup screens:
#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
- A Coolify instance with a stable, publicly reachable base URL, for example
https://coolify.example.com. - A GitHub account that can create and install a GitHub App in the required personal account or organization.
- The repository and branch you intend to deploy.
- A deployment server selected in Coolify, plus the application’s domain, build settings, and environment variables.
- If pull-request previews are needed, a plan for where preview deployments will be created and which repositories may receive them.
GitHub must be able to reach the Coolify endpoint from the internet. Private-only, loopback, or otherwise inaccessible addresses cannot receive the events required for automatic and preview deployments.
Create the GitHub App source in Coolify
1. Start a new GitHub App source
- In Coolify, open Sources.
- Select New source, then choose GitHub App.
- Enter a source name that identifies the GitHub account or organization it serves.
- Optionally enter the GitHub organization. Leave this blank when the app belongs to a personal account rather than an organization.
- For GitHub.com, choose Automated installation.
Automated installation is the shortest path for GitHub.com because Coolify can arrange the app credentials, callback information, permissions, and webhook integration as part of registration.
2. Enter the webhook endpoint correctly
Use the publicly reachable Coolify base URL, such as https://coolify.example.com. Do not append /webhooks. Coolify uses the base URL while configuring the GitHub App’s event delivery. An endpoint with the wrong path can leave repository access apparently functional while push and preview events fail to arrive.
Check the address from outside your private network before continuing. DNS, firewall, reverse-proxy, TLS, and authentication rules must allow GitHub’s requests to reach Coolify. The URL should remain stable; changing it later requires updating the source configuration and checking delivery again.
3. Choose preview-deployment permissions when needed
If pull-request previews are part of your workflow, set Preview deployment access to Read and update pull requests. The mandatory read permissions include:
- Repository contents
- Repository metadata
- Email addresses
Do not request pull-request write access merely because the repository is private. Select the preview setting only when Coolify needs to create or update preview deployments from pull-request events. For push-only production deployments, the preview permission is unnecessary.
Recommended Free Tools
4. Register the app with GitHub
- Select Register with GitHub in Coolify.
- When GitHub asks for an app name, enter a name that is unique on GitHub.
- Select Create GitHub App.
After registration, Coolify stores the generated App ID, client credentials, webhook secret, and private key. Treat these values as credentials: do not paste them into source files, commit them to the repository, or expose them in deployment logs.
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.
Install the app and limit repository access
Choose an installation scope
GitHub’s installation prompt lets you choose All repositories or Only select repositories. Selective access is the safer default when Coolify needs only a few projects: it prevents the app from listing or cloning unrelated repositories and limits the impact of a compromised credential.
Choose all repositories only when the account or organization deliberately wants a centrally managed Coolify integration for every repository. You can change the installation scope later in GitHub, but removing a repository immediately affects applications that depend on it.
Install and confirm the repository
- In GitHub’s repository-access prompt, select All repositories or Only select repositories.
- If using selective access, check every repository that Coolify should deploy.
- Select Install.
- Return to Coolify and confirm that the new GitHub App source is available under Sources.
If the repository does not appear when you later create an application, revisit the GitHub App installation and add that repository. A repository that was never selected cannot be loaded by Coolify, even when its owner and organization fields are correct.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Create a Coolify application from the private repository
- Open the target Coolify project and environment.
- Select + New.
- Choose Private Repository (with GitHub App).
- Select the deployment server.
- Select the GitHub App source you just created.
- Choose the repository and select Load Repository.
- Choose the branch that should deploy to this application.
- Set the build method and other build settings appropriate to the repository.
- Configure the application’s domain and environment variables.
- Deploy the application once the configuration is complete.
Loading the repository proves that the app can authenticate and read it. It does not by itself prove that a later push will trigger a deployment; that depends on the branch and auto-deploy configuration described next.
Turn on deploy-on-push and verify the first event
Check the auto-deploy mode
Applications created through a GitHub App normally use Deploy on push (webhooks). Verify the setting explicitly:
- Open the application in Coolify.
- Go to Advanced, then Deployment.
- Under Auto deploy, choose Deploy on push (webhooks) if the application is set to manual deployment.
The configured branch matters. A push to a different branch does not update the production application unless that branch is assigned to a preview deployment or a separate application.
Send a controlled test push
- Make a small commit on the exact branch configured for the application.
- Push it to GitHub.
- Open Coolify’s Deployment Logs.
- Confirm that a webhook deployment appears and that its commit matches the test push.
Use a deliberate test commit rather than assuming that any recent repository activity should deploy. This verifies the branch mapping, event delivery, repository access, and build configuration in one pass.
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.
Deploy only relevant monorepo changes with Watch Paths
Monorepos often contain several applications. A push that changes documentation or an unrelated package should not necessarily rebuild every service. Coolify’s Watch Paths setting filters provider webhook events according to the files changed in the event.
Configure the patterns
- Open the application.
- Go to General, then Build.
- Enter one watch-path pattern per line.
Patterns support *, **, ?, and negation with !. The last matching pattern wins. For example:
apps/api/**
packages/shared/**
!apps/api/**/*.mdWith these rules, changes under apps/api or packages/shared qualify, while Markdown-only changes under apps/api are excluded because the negated rule is evaluated later.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Understand what Watch Paths do not filter
Watch Paths apply to provider webhook events that include changed-file information. They do not block a manual deployment started from the Coolify dashboard, and they do not block an authenticated Deploy Webhook call. Test the rules with a documentation-only commit before depending on them for production cost or capacity control.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot a push that did not deploy
Work from the outside in: verify the GitHub installation, event reachability, Coolify’s mode, branch selection, and the logs. This avoids changing build settings when the event never reached the application.
The repository is missing from Coolify
- Open the GitHub App installation settings.
- Confirm that the repository is included under Only select repositories, or that the installation uses All repositories.
- Confirm that the source in Coolify points to the intended personal account or organization.
- Reload the repository list and try Load Repository again.
Removing repository access prevents new clones and webhook deployments for applications that use that GitHub App.
The repository loads, but no webhook deployment appears
- Check that the webhook endpoint is the public Coolify base URL and does not end in
/webhooks. - Confirm that GitHub can reach the endpoint through DNS, firewall, proxy, and TLS configuration.
- In Advanced > Deployment, verify Auto deploy is Deploy on push (webhooks).
- Confirm that the push targeted the branch configured for this application.
- Review Coolify Deployment Logs and GitHub’s webhook delivery status.
A successful push in GitHub is not evidence that Coolify received or accepted the event. The two log locations provide separate checks: GitHub shows delivery, while Coolify shows whether a qualifying event became a deployment.
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.
A webhook arrives, but the wrong application deploys
- Compare the pushed branch with each application’s configured branch.
- Check whether the repository is a monorepo with multiple applications and overlapping Watch Paths.
- Review the changed files against the last-match-wins rules.
- Look for a preview application or another environment that is intentionally assigned to that branch.
Pull-request previews do not update
- Confirm that Preview deployment access is set to Read and update pull requests.
- Verify the mandatory read permissions for repository contents, metadata, and email addresses.
- Confirm that GitHub can reach the same public base URL used by the source.
- Check GitHub delivery records and Coolify logs for the pull-request event.
The app was working and then stopped
Start by checking whether repository access was changed or revoked in GitHub. A removed repository, deleted installation, changed endpoint, or switched auto-deploy mode can stop new deployments without changing the application’s build definition. Re-authorize or restore the repository scope, then send a new test commit and inspect both delivery and deployment logs.
Alternatives when a GitHub App is not suitable
Coolify supports several source patterns. The right choice depends on repository privacy, how broadly access should be granted, where builds run, and how much webhook configuration you want to maintain.
| Approach | Repository access | Scope | Pull-request previews | Webhook effort | Where builds run |
|---|---|---|---|---|---|
| Public repository over HTTPS | Public code only | Anyone with the URL can read it | Not provided by repository authentication alone | Manual Git webhook if automatic deployment is required | Coolify |
| Deploy key | Private repository over SSH | One repository | Not integrated by the key itself | Separate repository webhook or external workflow required | Coolify |
| GitHub App | Public or private repositories | One, selected, or all repositories, depending on installation | Integrated push and pull-request events | Automated installation handles the integration | Coolify |
| GitHub Actions | Repositories available to GitHub Actions | Controlled by the workflow and repository permissions | Handled by the workflow rather than Coolify’s GitHub App integration | Workflow must trigger the deployment | GitHub Actions builds and publishes an image before Coolify deploys it |
When a deploy key is the better fallback
A deploy key grants one SSH key access to one private repository and should normally be read-only. It is useful when an app cannot be installed or when you intentionally want one-repository scope. The key supplies repository access only; it does not create automatic deployment events. Add a repository webhook or use an external workflow separately if pushes must trigger Coolify.
When to use a manual Git webhook
For a public-URL or deploy-key application, create a manual Git webhook in Coolify, copy its GitHub URL and secret, and add them under GitHub repository Settings > Webhooks. Select the push event, keep SSL verification enabled, and set Coolify to Deploy on push (webhooks). The secret entered in GitHub must match Coolify’s value and contain at least 16 characters.
This fallback has two independent credentials: the deploy key authenticates repository reads, while the webhook secret authenticates deployment notifications. Rotating one does not replace the other.
Security and maintenance checklist
- Use Only select repositories unless organization policy requires all-repository access.
- Grant pull-request update permission only when preview deployments need it.
- Keep the generated private key, client credentials, App ID, and webhook secret out of repositories and logs.
- Use a read-only deploy key when a deploy key is the chosen fallback.
- Keep SSL verification enabled for manual Git webhooks.
- Record which Coolify applications depend on each GitHub App source before changing its installation scope.
- After changing the public Coolify URL, verify GitHub delivery and run a controlled push test.
- For monorepos, document Watch Paths and retest them after moving directories or renaming packages.
Operational verification checklist
Use this sequence after initial setup, a permission change, or an endpoint migration:
- Confirm the GitHub App installation includes the target repository.
- Confirm the Coolify source uses the public base URL without
/webhooks. - Confirm required repository and, if applicable, pull-request permissions.
- Confirm the application points to the intended server, repository, and branch.
- Confirm Advanced > Deployment > Auto deploy is Deploy on push (webhooks).
- Review Watch Paths when the repository is a monorepo.
- Push a small commit to the configured branch.
- Check GitHub webhook delivery and Coolify Deployment Logs for the same commit.
A GitHub App is usually the cleanest Coolify integration for private repositories and preview deployments because installation scope, credentials, and provider events are managed together. The setup is complete only when the repository is installed, GitHub can reach the public base URL, the application watches the intended branch, and the deployment log confirms a real push event.
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.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute
