iTechGuides 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.
You can deploy a public GitHub repository in Coolify without creating a GitHub App, Git source, or deploy key. Create an application from the repository’s HTTPS URL, select the build pack that matches the project, expose the port used inside the container, configure environment variables, attach a domain, and deploy. Coolify builds the source on a server you control, then routes the domain to the resulting application.
The two settings that most often explain an apparently successful but unreachable deployment are the internal container port and the domain’s application mapping. A healthy container is not enough if the process listens on a different port or the hostname is attached to another service.
What you need before creating the application
Coolify is self-hosted. You supply a connected server and remain responsible for its capacity, operating system, network access, DNS, updates, and firewall policy. The platform documentation describes it as “an open source, self-hostable platform for deploying and managing applications, databases, and services on servers you control.”
For a dashboard deployment, have these values ready:
#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: 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.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
- A Coolify account with access to the target project and environment.
- A connected server on which Coolify can build and run the application.
- The public GitHub repository’s HTTPS URL.
- The branch or tag to deploy.
- The build pack that matches the repository.
- The port on which the application listens inside its container.
- Any required environment variables, including production secrets.
- A hostname you can route to the application, unless you will use a configured wildcard or generated domain.
The official CLI workflow additionally requires a verified CLI context with permission to create and deploy applications, plus the target project UUID, server UUID, and environment. The dashboard’s Application creation form collects the same operational information.
Do public repositories need a GitHub App or deploy key?
No. A public repository can be fetched directly over HTTPS. When you create the application, enter the repository URL and branch; you do not need to create a Git source connection or install a deploy key merely to read public code.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThis does not make every GitHub integration unnecessary. Automatic deployments, provider webhooks, or access to private repositories may require the documented GitHub App or another authenticated integration. That is a separate requirement from the first deployment of a public repository.
Choose the build pack before you deploy
The build pack determines how Coolify turns repository files into a runnable application. Select it from the repository’s actual structure, not from the language name alone.
| Build pack | Best fit | Decision and trade-off |
|---|---|---|
| Nixpacks or Railpack | Conventional language projects with recognizable manifests | Fast source detection and fewer files to maintain; less explicit control over the resulting image. |
| Static | Projects that produce static files such as a built front end | Simple serving model, but the build and publish directory must be correct. |
| Dockerfile | A repository containing a Dockerfile or requiring custom operating-system packages, runtime versions, or multi-stage builds | Maximum image control, with the responsibility to maintain the Dockerfile. |
| Docker Compose | A repository defining several cooperating services | Preserves the service topology, but each service may need its own port, domain, storage, and log selection. |
Nixpacks and Railpack are convenient when the repository has a supported manifest and conventional commands. Choose Dockerfile when detection would omit a system dependency or when you need exact control over build stages. Choose Compose only when the repository’s services genuinely need to run together; it adds routing and operational decisions that a single application does not require.
Coolify builds source-based applications on the deployment server by default. Supported configurations can use a dedicated build server and registry instead. If a rebuild appears to reuse an unwanted Docker layer, a force deploy is available to rebuild without Docker’s build cache.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →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
Deploy the repository from the Coolify dashboard
1. Start a public-repository application
- Open the target project and environment in Coolify.
- Choose the option to create a new application from a public Git repository.
- Paste the repository’s HTTPS URL. Do not add credentials to the URL.
- Select the branch or tag that should be deployed.
Use the repository URL exactly as GitHub presents it. If the project is a monorepo, identify the directory that contains the relevant manifest, Dockerfile, or Compose file before continuing.
2. Set the source location and build context
If the application form exposes a base-directory or build-context field, point it at the subdirectory containing the application’s build files. A wrong base directory can make a valid repository look as if its package manifest, Dockerfile, or Compose file is missing.
For a static project, also identify the directory that contains the generated files after the build. The static build pack must serve the output directory, not the repository’s source directory.
3. Select the build pack
Choose Nixpacks or Railpack for a conventional source project, Static for files that will be served without a long-running application runtime, Dockerfile when the repository supplies an explicit image definition, or Docker Compose for a multi-service repository. If the first source build fails, verify this choice before changing application code.
4. Enter the exposed container port
Set the exposed port to the port on which the process listens inside the container. This is not an arbitrary host port and is not necessarily the port you would use when testing the application on your laptop.
For example, if the application process listens on port 8080 inside its container, expose 8080 in Coolify. Coolify can then route the configured domain to that target. If the process listens on 3000 but 8080 is exposed, the container may be running while the public request has no responding service.
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.
Check the project’s start command, Dockerfile, framework configuration, or Compose service definition to determine the real listening port. The process must also listen on the container’s reachable interface rather than only on a loopback address.
5. Add environment variables and secrets
Open the Environment Variables area and create the variables required by the application. Keep passwords, API keys, signing keys, and other secrets in Coolify’s secret handling rather than committing them to the repository or putting them in shell history.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Coolify’s CLI can create an individual variable or synchronize values from a dotenv file. Treat a dotenv file used for synchronization as sensitive: restrict its permissions and avoid echoing it in automation logs.
Separate values needed while building from values needed only when the container runs. A front-end build may embed selected public configuration during compilation, while a server process may read its database URL at runtime. After changing a variable that affects the container, deploy or restart the application; saving the field alone does not necessarily replace the running container.
6. Configure the domain
In Domains, add the public hostname that should route to this application. Where your Coolify server is configured for it, you can use a wildcard or generated domain instead of entering a custom hostname.
The domain and port perform different jobs:
- The domain identifies the public hostname and the application to which requests are routed.
- The exposed port identifies the destination port inside the application container.
Make sure the hostname resolves to the Coolify server’s public endpoint and that the hostname is attached to this application rather than another service. A correct DNS record cannot compensate for an incorrect Coolify domain mapping, and a correct mapping cannot help if the hostname points elsewhere.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
7. Add a health check only when the endpoint is real
If you configure a health check, use a path and port that the application actually serves. A check aimed at a nonexistent path can mark an otherwise working container unhealthy. Change the health-check settings together with the application configuration, then deploy or restart so the running container uses them.
8. Deploy and watch the build
Start the deployment from the application page. Follow the timestamped deployment output rather than relying only on the final status. The log should show source retrieval, the selected build process, image creation, container startup, and any health-check result.
A failed source build does not replace the currently running version. This behavior lets you investigate the new build while the last successful version remains available.
Recommended Free Tools
Deploy with the Coolify CLI
The CLI is useful for repeatable deployments and automation, but the context must be verified first and must have permission to create and deploy applications. Gather the project UUID, server UUID, environment, public repository URL, branch, build pack, and internal container port before running commands.
The documented command sequence is:
- Create the public-repository application with
coolify app create public, supplying the project, server, environment, repository, branch, build-pack, domain or health-check options as needed, and the required exposed port. The port is supplied with--ports-exposes. - Create an environment variable with
coolify app env create, or synchronize a dotenv file withcoolify app env sync. - Deploy the created application with
coolify deploy uuid <application-uuid>.
The final command has this exact form:
coolify deploy uuid <application-uuid>Do not pass secrets as command-line arguments when automation could expose them in shell history or process listings. Use Coolify’s environment-variable handling instead. In a script, also capture the deployment result and inspect the application status and logs rather than assuming that a successful command means the public URL is reachable.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How ports, domains, and redeploys fit together
There are three separate layers to check:
- Application process: the program starts and listens on its configured internal port.
- Container exposure: Coolify is configured with that same internal port.
- Public routing: the domain is assigned to the application and resolves to the server.
Changing a port, domain, network, storage setting, resource limit, health check, or environment variable changes the desired configuration. Deploy or restart after saving those changes so Coolify can create or replace the running container. Build-file changes require a deployment that creates or reuses an image.
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.
If you only need to re-run a build and suspect stale Docker layers, use a force deploy. It is a rebuild control, not a substitute for fixing a wrong branch, base directory, port, or domain.
Verify a deployment before declaring it live
- Open the deployment records and confirm the latest deployment reached a successful state.
- Check the application status and container state.
- Read the timestamped application logs around startup. Look for the actual listening port, migration errors, missing variables, and process exits.
- Request the configured domain from a browser or an HTTP client.
- If the response fails, test the service path and routing again rather than immediately rebuilding the image.
For Docker Compose, select the specific service when reading logs. The database, worker, reverse proxy, and web service can have different health and port behavior; a healthy database container does not prove that the web service is reachable.
Troubleshoot the common failure modes
| Symptom | What to inspect | Correction |
|---|---|---|
| The build fails before a new container starts. | Deployment logs, selected build pack, branch, base directory, and repository build files. | Choose the build pack that matches the repository, correct the source location, and fix the reported build error. The previously running version remains in place after a failed source build. |
| The container is healthy but the URL times out or returns a gateway error. | The process’s internal listening port, Coolify’s exposed-port value, domain assignment, and hostname resolution. | Make the exposed port match the process, attach the domain to the correct application, and verify that the hostname reaches the Coolify server. |
| A configuration change has no visible effect. | Whether the change was only saved or was followed by a deploy or restart. | Deploy or restart after changing variables, ports, domains, health checks, networks, storage, resource limits, or build settings. |
| A Compose deployment appears partly working. | Logs for the particular service receiving the request and the service’s own port and health state. | Select the relevant Compose service, correct its routing, and redeploy the stack. |
| Secrets appear in logs or command history. | Shell commands, dotenv synchronization output, and build scripts that print variables. | Move secrets into Coolify’s environment-variable or secret handling and remove logging of sensitive values. Avoid passing them as command-line arguments. |
| A rebuild still appears unchanged. | Whether Docker cache reused an earlier layer and whether the intended branch or commit was deployed. | Confirm the source revision, then use a force deploy when a cache-free rebuild is required. |
Automatic deployments after the first successful release
A manual deployment is sufficient for testing a public repository or releasing a pinned branch on demand. For automatic deployments, use Coolify’s documented webhook or GitHub App integration path when the repository and provider access model require webhooks.
Keep the initial public-repository access decision separate from webhook authentication: public code can be fetched over HTTPS without a deploy key, while an automated provider callback may still need an integration that can notify Coolify of a new commit.
Operating the server responsibly
Because Coolify is self-hosted, the deployment is not an all-inclusive hosting plan. You choose and maintain the server, its storage, network exposure, backups, monitoring, and update policy. Capacity planning should account for both the application’s runtime and source builds; a build performed on the deployment server consumes that server’s CPU, memory, disk, and network resources unless you configure a supported dedicated build server and registry.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use separate environments when you need to test a branch before promoting it, restrict who can edit production variables, and keep the repository’s deployment branch deliberate. These controls do not change the public-repository workflow, but they prevent an otherwise correct application from being deployed to the wrong place.
Quick Recap
A repeatable deployment checklist
- Public repository URL uses HTTPS and the intended branch is selected.
- Project, environment, and connected server are correct.
- Build pack matches the repository’s files and service topology.
- Base directory and static publish directory, if applicable, are correct.
- Exposed port equals the process’s internal listening port.
- Required environment variables are present and secrets are not committed.
- Domain resolves to the Coolify server and is assigned to this application.
- Health-check path and port, if configured, are served by the application.
- Deployment logs show a successful build and startup.
- A deploy or restart follows configuration changes.
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.
