Is there a way to make localhost as build server?

[LynxTR]

I am managing a remote server via coolify instance deployed to the hetzner (2 servers in total), but deployments giving the remote one high cpu spikes so i would like to avoid that without buying a separate server for builds. Is there a way to make build in the coolify server?

https://coolify.io/docs/knowledge-base/server/build-server/

[arcofs]

Looking for the answer to this question too. I have been using localhost for many resources, now setup a remote server, but need the localhost to act as a build server, as this is the main machine with the horsepower (not the remote VPS)

[ahmedd-osama]

I have a similar 2-server setup and I am looking for a solution to this as well. I tested out a the Build Server Method that needs an extra server to act as a build server and also needs setup with a container registry to push the images to. I would say the docs are a bit lacking in terms of clarity on how to set up this as of this point. but every thing seems to be working fine with this solution. The only downside is that you'll have to either subscribe to a container registry or host your own, and you'll have to get another build server only for builds.

[KianAnbarestani]

@LynxTR
Yes, you can offload builds to your Coolify dashboard server to reduce CPU load on your remote node. Go to the remote server’s settings in Coolify and enable “Use different server to build,” then select your dashboard server. This will run builds on the dashboard node and push the final image to the app server. No need to buy extra servers for this.

[leon2811-be]

Any updates on this? Would be really cool to use the localhost as build server

[mbanerjeepalmer]

I asked the same question in the Discord: https://discord.com/channels/459365938081431553/1377964787622871070/1377964787622871070

The answer was no, you can't put your Coolify instance and builds on server A, and applications server B. You have to put Coolify and applications together, and only a separate build server.

I agree with others that I would prefer to have builds and Coolify together, and separate applications.

[djsisson]

cant you add a new server and just select your localhost ip again but just tick buildserver ? you can then build on localhost, (you will need a registry of some sort of course)

[leon2811-be]

@djsisson Did you try this?

[djsisson]

yes jsut

[leon2811-be]

What do you mean with registry?

[djsisson]

Once you build on a different server you need to use a registry to host your images, otherwise how would your other servers get the built image that were created on the build server

There is a registry service or you can use one of the docker hubs like ghcr.io or dockerhub

[JLouisa]

Steps I followed to setup my local linux Ubuntu dev machine as build server:

Guide: How to Use a Local PC as a Coolify Build & Deployment Server

• Coolify Host: Your main server running the Coolify UI (e.g., a VPS in the cloud).
• Local Server: Your powerful local PC (e.g., running Ubuntu Desktop) that will build and run applications.
• Result: Deploy applications from the Coolify UI directly onto your Local Server.

Step 1: Secure Network Connectivity with Tailscale

Coolify needs a secure and reliable way to connect to your local PC. Exposing SSH or Docker ports directly to the internet is extremely dangerous. A private overlay network like Tailscale is the perfect solution.

1. Install Tailscale on the Coolify Host:

   ssh root@<coolify-host-ip>
   curl -fsSL https://tailscale.com/install.sh | sh
   sudo tailscale up
   # Follow the URL to authenticate in your browser.

2. Install Tailscale on the Local Server:

   curl -fsSL https://tailscale.com/install.sh | sh
   sudo tailscale up
   # Follow the URL to authenticate.

3. Verify IPs: Go to your Tailscale Admin Console. Note the 100.x.y.z IP address for your Local Server. You will need this later.

Step 2: Prepare the Local Server

We need to install all the necessary software and configure permissions.

1. Install Docker:

   # Run all of these on your local PC
   sudo apt update
   sudo apt install docker-ce docker-ce-cli containerd.io

2. Authenticate with Docker Hub: Your server needs to pull base images and push your final images.

   # Log in with your Docker Hub username and a Personal Access Token (PAT).
   docker login -u <your-docker-id>

3. Install SSH Server: Coolify will connect to this machine via SSH.

   sudo apt install openssh-server
   sudo systemctl enable --now ssh
   sudo ufw allow ssh # Allow SSH through the firewall if ufw is active.

4. Grant Sudo Permissions without a Password: Coolify needs to run sudo commands without being prompted for a password.
   • IMPORTANT: Use visudo to safely edit the sudoers file.

     sudo visudo

   • Scroll to the bottom of the file and add this line, replacing your_local_username with your actual username on the local PC:

     your_local_username   ALL=(ALL) NOPASSWD: ALL
     

   • Save and exit (Ctrl+X, Y, Enter).

Step 3: Configure SSH Authentication

Coolify needs its own unique "ID card" (SSH key) to access your local server.

1. Create a New SSH Key on the Coolify Host:

   • SSH into your coolify-host.
   • This command creates a new key pair without a passphrase, which is essential for automation.

     ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519 -N ""

2. Get the Public Key: This is the "lock" that goes on your local server's door.

   # On coolify-host, display the public key.
   cat ~/.ssh/id_ed25519.pub
   # Copy the entire single line of output.

3. Authorize the Key on the Local Server:

   • SSH into your local server.
   • This one-liner adds the public key to the list of authorized "visitors". Replace PASTE_PUBLIC_KEY_HERE with the key you just copied.

     mkdir -p ~/.ssh && chmod 700 ~/.ssh && echo "PASTE_PUBLIC_KEY_HERE" >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys

   • Verify Permissions: The sshd server is very strict. Double-check permissions with ls -ld ~ ~/.ssh ~/.ssh/authorized_keys. They should look like drwxr-xr-x, drwx------, and -rw------- respectively.

4. Get the Private Key: This is the "key" that Coolify will hold.

   # On coolify-host, display the private key.
   cat ~/.ssh/id_ed25519
   # Copy the entire block, including the BEGIN and END lines.

Step 4: Add the Local Server to Coolify

Now, we tell Coolify about our new server.

1. In the Coolify UI, go to the Server page and click "New Server".
2. Fill out the form:
   • Name: A descriptive name, like Local Build PC.
   • IP Address/Domain: The Tailscale IP of your local PC (e.g., 100.x.y.z).
   • User: Your username on the local PC (e.g., your_local_username).
   • Port: 22.
3. For the Private Key, click "New Private Key":
   • Give it a name, like Coolify Host Key.
   • Paste the private key you copied in the previous step.
   • Click "Continue".
4. Click "Save" on the server form. The validation should now pass and show "Server is reachable."

Step 5: Configure Your Application and Deploy!

You are ready to deploy.

1. Go to your Application in Coolify.
2. In the Configuration -> Build settings, make sure your Docker Image Name includes your Docker Hub username. For example:
   • Incorrect: my-cool-app
   • Correct: <your-docker-id>/my-cool-app
3. In the Configuration -> General settings, select your new server from the Destination dropdown menu.
4. Save the configuration and click Deploy.

Coolify will now SSH into your local PC, run the Docker build using its full resources, push the correctly-named image to Docker Hub, and then run the container on that same machine.

Congratulations! You now have a fully functional, powerful, local build and deployment pipeline integrated with Coolify.

Hope this helps

[styxlab]

Thanks a lot for this excellent guide which I now verified with my own setup. Instead of using the proprietary tailscale service, I recommend to use the free and open-source wireguard service. In principle, it should be possible to spin-up the wireguard service on the coolify host directly, however, I was not able to connect the wireguard network to the collify network, therefore I had to install it directly on the coolify host machine.

If you have a powerful workstation for development, running all builds on your workstation is the fastest and most cost effective setup while offloading the build spikes from your production machines.

[AKRking]

Is it possible if im running windows pc?