Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
Coolify can deploy a GitLab project in three ways: clone a public repository over HTTPS, clone a private repository with an SSH deploy key, or use a GitLab App integration. The GitLab App is the most integrated option for private repositories, repository selection, push events, and merge-request previews. A deploy key is simpler when one Coolify application needs read-only access to one private project. A public HTTPS repository needs no Git credentials.
Whichever source you choose, the Coolify server must reach GitLab and run Docker workloads. Automatic production deployments also depend on the application’s configured branch and the Deploy on push (webhooks) setting. The sections below show the setup for each path, how events trigger builds, and how to diagnose failures without confusing Git credentials with container-registry credentials.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the GitLab connection that fits your repository
Start by deciding how Coolify should authenticate and how much GitLab event integration you need. The repository’s visibility is only one part of the decision; preview deployments, access scope, and operational control matter just as much.
| Connection method | Repository access | Authentication scope | Events and previews | Best fit |
|---|---|---|---|---|
| Public HTTPS URL | Public GitLab repository | No Git credential required for cloning | Manual webhook configuration for automatic deployments; merge-request events can be enabled for previews | A public project or a repository where source visibility is acceptable |
| SSH deploy key | Private GitLab repository | One repository, read-only deploy-key access | Manual webhook configuration; push and merge-request events are selected in GitLab | One private project, or an environment where an App/OAuth integration is unavailable |
| GitLab App | Private or public projects available through the integration | App-managed repository access | Integrated provider events, including push and merge-request events; no separate manual Git webhook URL is needed | Private repositories, repository browsing, and preview workflows |
A GitLab App still needs the application’s automatic-deployment setting enabled and a push to the branch assigned to that application. Integration events do not make every branch deploy to the same production application.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Check the prerequisites before creating the application
- A running Coolify instance and connected server: Coolify runs applications as Docker containers on a connected server. That server needs outbound reachability to GitLab and enough capacity to build or pull the application image.
- The GitLab project and target branch: Decide which branch represents the deployment you are configuring. The Coolify application tracks a selected branch; a push to another branch will not update that production application.
- A supported build path: Git-based applications can use Nixpacks, Railpack, Static, Dockerfile, or Docker Compose build paths. Your repository should contain the files required by the path you select.
- Event and credential ownership: Have project-level permission in GitLab to add deploy keys or webhooks, and keep any private key or webhook secret available for entry in Coolify and GitLab.
For self-managed GitLab, the App setup also requires the GitLab instance URL and its API URL. A self-managed installation must be reachable from the Coolify server for both API communication and source access.
Connect a public GitLab repository over HTTPS
A public repository is the shortest path because Coolify can clone its HTTPS URL without a deploy key or App credential. You still need a deployment trigger if you want pushes to build automatically.
- Create a Coolify application and choose the public Git repository source.
- Enter the repository’s public HTTPS URL and choose the branch that should represent this application’s production version.
- Select the build path that matches the project: Nixpacks, Railpack, Static, Dockerfile, or Docker Compose. Save the application configuration.
- Run an initial deployment from Coolify. In the deployment log, confirm that Coolify clones the expected repository and checks out the selected branch or commit.
- Configure automatic deployment if required. Copy the webhook URL shown by Coolify, create a secret of at least 16 characters, and enter the same URL and secret in GitLab under Settings > Webhooks.
- Enable the event types in GitLab. Enable Push events for branch deployments; enable Merge request events as well when the application is intended to create previews.
- Set the Coolify trigger at Advanced > Deployment > Auto deploy to Deploy on push (webhooks). Use GitLab’s webhook test, then push to the configured branch and inspect Coolify’s Deployment Logs.
Public source access does not remove the need for network reachability. If GitLab cannot deliver the webhook to Coolify, or Coolify cannot reach the repository URL, the source can be public and deployments will still fail.
Deploy a private repository with an SSH deploy key
A deploy key gives one GitLab project a public key that corresponds to a private key held by Coolify. The usual model is read-only access to one repository, which limits the blast radius compared with a credential that can browse many projects.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
1. Create or store the private key in Coolify
In Coolify’s source or application credentials area, create a deploy-key credential or store an existing private key. Keep the private key confidential; it is the value Coolify uses when it clones the repository. Do not paste the private key into GitLab’s deploy-key field—GitLab receives the matching public key.
2. Add the public key to the correct GitLab project
Open the project in GitLab and go to Settings > Repository > Deploy keys. Add the public key that matches the private key saved in Coolify. Attach it to the project that actually contains the branch you intend to deploy. A key added to a different project will authenticate successfully nowhere useful for this application.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →3. Use the repository’s SSH URL
Copy the project’s SSH clone address, for example git@gitlab.com:group/project.git. Preserve the group and project path exactly; an HTTPS URL or a misspelled namespace will not use the deploy key you configured.
4. Create the Coolify application
- Create a new Coolify application and choose Private Repository (with deploy key).
- Select the deploy key credential and paste the repository SSH URL.
- Choose the deployment branch and the appropriate build path.
- Save, deploy once, and read the deployment log. A successful source phase should show the expected repository being cloned and the requested commit being checked out.
5. Add a manual webhook for push deployments
A deploy key authenticates cloning; it does not itself notify Coolify when a commit arrives. Copy the webhook URL from the Coolify application, save a secret of at least 16 characters, and enter both values under the project’s Settings > Webhooks in GitLab. Enable Push events for normal branch deployments and Merge request events when previews are needed. In Coolify, set Advanced > Deployment > Auto deploy to Deploy on push (webhooks). Test delivery in GitLab, push to the configured branch, and follow the resulting Deployment Logs.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Use a GitLab App for integrated private-repository access
The GitLab App is suited to private HTTPS cloning, browsing available repositories, and provider events. It is also the most convenient route when several projects or merge-request previews are part of the workflow.
Create the source in Coolify
- In Coolify, create a GitLab App source.
- For self-managed GitLab, enter the GitLab URL and the GitLab API URL requested by Coolify. Use the instance’s actual addresses, not a public GitLab address copied from another environment.
- Complete the App authorization and save the source.
Connect project events
For each GitLab project that will send events, add the webhook URL and matching secret token supplied by Coolify. This is the App’s provider-event connection; it is different from manually inventing a second webhook endpoint. Enable Push events for branch deployments. Enable Merge request events when the application should receive merge-request activity for preview deployments.
Create the application from the App source
- Create a new Coolify application using the GitLab App source.
- Select the repository from the projects exposed by the integration.
- Select the branch for this application and choose its build path.
- Save and deploy.
- Open the deployment log and verify that Coolify cloned the selected repository and checked out the requested commit.
With the GitLab App, you do not need to add a separate manual Git webhook URL for the application. You still must set Auto deploy to Deploy on push (webhooks) and push to the application’s configured branch for automatic production deployments.
Configure manual GitLab webhooks correctly
Manual webhooks apply to public-URL and deploy-key applications. The URL and secret are a pair: GitLab sends the event to the URL, and Coolify verifies that the request carries the secret it saved.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
- Open the Coolify application’s deployment or webhook settings and copy its webhook URL.
- Create a secret that is at least 16 characters long and save it in Coolify.
- In GitLab, open the project and choose Settings > Webhooks.
- Enter the exact Coolify URL and the exact same secret.
- Enable Push events. Enable Merge request events for preview deployments.
- In Coolify, open Advanced > Deployment > Auto deploy and select Deploy on push (webhooks).
- Use GitLab’s webhook test feature. Confirm the delivery response, then push a commit to the configured branch.
- Open Coolify’s Deployment Logs and check that the event starts a deployment and that the expected commit is checked out.
Do not assume that a successful webhook test proves a successful build. The test validates delivery; the deployment log validates source access, checkout, build, runtime configuration, and container replacement.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Understand branches, pushes, and merge-request previews
Production branch behavior
Each Coolify application has a configured branch. A push to that branch can trigger its automatic deployment when the webhook setting is enabled. A push to another branch does not update that production application unless you configure another application or otherwise assign that branch separately.
Preview deployments
Preview workflows depend on Merge request events. Enable those events in GitLab for a manual webhook or in the project’s GitLab App event connection. The application must also be configured for the preview behavior you want; merely checking the event box does not turn every merge request into a production deployment.
Commit verification
After any first deployment or trigger change, inspect the log for two source details: the repository path and the checked-out commit. This catches a wrong project, wrong branch, stale event, or a URL that points to a different namespace before you troubleshoot the build itself.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
What Coolify does after GitLab triggers a deployment
“A deployment combines configuration saved in Coolify with a trigger such as Deploy, Redeploy, a Git webhook, or an API request.”
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Once the trigger is accepted, Coolify resolves the requested source and version, then builds or pulls the necessary image. Depending on the project configuration, the build can use Nixpacks, Railpack, Static, Dockerfile, or Docker Compose. Coolify applies the saved runtime configuration and updates the running containers on the connected server.
This sequence explains why a deployment can fail after GitLab reports successful delivery. GitLab’s responsibility ends with sending the event; Coolify still needs valid source credentials, a reachable repository, a usable build definition, and a server capable of running the resulting Docker workload.
Keep Git credentials separate from container-registry credentials
Repository authentication and image-registry authentication solve different problems. A GitLab App, HTTPS access, or SSH deploy key allows Coolify to clone source code. If the application later pulls a private container image from GitLab Container Registry, Coolify needs separate registry credentials for that image. A working deploy key does not grant registry access, and registry credentials do not automatically fix a failed Git clone.
- Use the narrowest Git access that meets the deployment requirement: a public URL, a one-project read-only deploy key, or App-managed access.
- Store private keys and webhook secrets only in the systems that need them.
- For self-managed GitLab, verify that the Coolify server can reach both the GitLab instance and the API endpoint used by the App.
- Review branch selection whenever a project changes its release flow; events for an unselected branch will not update the production application.
Troubleshoot a GitLab-to-Coolify deployment
| Symptom | Likely cause | What to check |
|---|---|---|
| No deployment starts after a push | Webhook delivery, event selection, or Auto deploy setting | Confirm the webhook URL is reachable from GitLab, Push events are enabled, and Coolify is set to Deploy on push (webhooks). |
| GitLab reports a webhook error | Coolify cannot be reached from GitLab | Check the Coolify server’s public reachability, routing, firewall, and the delivery result shown in GitLab. |
| Webhook arrives but is rejected | Secret mismatch | Compare the Coolify secret with GitLab’s saved secret character for character. Replace both values if necessary, then retest. |
| Push is delivered but the wrong code deploys | Wrong repository, branch, or commit | Check the application’s repository and branch, then verify the cloned repository and checked-out commit in Deployment Logs. |
| SSH clone fails | Public key attached to the wrong project, wrong private key, or malformed SSH URL | Confirm the matching public key is under the target project’s Settings > Repository > Deploy keys, select the corresponding private key in Coolify, and recheck the SSH URL such as git@gitlab.com:group/project.git. |
| Private HTTPS App source cannot be listed or cloned | App URL/API configuration or project authorization | For self-managed GitLab, verify both the GitLab URL and API URL; confirm the project is authorized in the App connection. |
| Source clones but the build fails | Build path or repository files do not match | Review whether Nixpacks, Railpack, Static, Dockerfile, or Docker Compose matches the repository, then read the build portion of the deployment log. |
| Build succeeds but a private image cannot be pulled | Missing registry credentials | Configure credentials for the private container image separately from Git credentials. |
Use a fixed order when diagnosing: first delivery, then secret validation, then event and branch selection, then source authentication, and finally build or runtime behavior. GitLab’s webhook delivery result and Coolify’s Deployment Logs provide the two independent views needed to locate the failing stage.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA practical decision framework
- Is the repository public? If yes, use its HTTPS URL unless you need App-managed browsing or event integration.
- Is it private and limited to one project? Use a read-only deploy key when a small, explicit trust boundary is preferable.
- Do you need private HTTPS cloning, repository selection, or merge-request previews across an integrated workflow? Use the GitLab App.
- Do you need automatic deployments? Configure the relevant webhook path, enable the right event, and set Deploy on push (webhooks).
- Does the project pull private images? Add registry credentials independently; do not treat repository authentication as registry authentication.
The reliable end state is easy to verify: GitLab can deliver the selected event, Coolify accepts it with the matching secret or App connection, the application’s branch is the one you intended, and Deployment Logs show the expected repository and commit before the build begins.
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.
