Warning
This guide has moved!
It is now maintained in the official Wasp docs: 👉 https://wasp.sh/docs/guides/deployment/coolify
This gist is archived and will no longer be updated.
Last active
February 13, 2026 10:36
-
-
Save infomiho/ad6fade7396498ae32a931ca563a4524 to your computer and use it in GitHub Desktop.
Deploying Wasp apps to Coolify
Self-hosting is a great way to have control over your deployment infrastructure (you own the data) and a great way to keep the costs down (you pay a fixed amount per month). One of the smoothest way to manage your self-hosted deployment is Coolify.
Deploying Wasp apps to Coolify is straightforward:
- create your Coolify apps (client, server and db)
- build your app's Docker images (e.g. using Github Actions),
- trigger Coolify to pull the Docker images and deploy them.
It'll take you ~1 hour depending on your level of experience with servers and Github Actions.
You should have Coolify installed and set up on your server. I'll be using Hetzner to rent my server.
Follow the Coolify install instructions: https://coolify.io/self-hosted
To get Coolify apps working with your domain - you'll need to point a A record to your server IP:
-
To use
myapp.comas your client domain, point theArecord with the value of@to your server IP. -
To use
api.myapp.comas your server domain, point theArecord with the value ofapito your server IP.
We'll set up the domains for our server and client apps below.
Tip
You can point an A record with value of coolify to your server IP and set Instance's Domain in the Settings as https://coolify.myapp.com so you can access the Coolify dashboard via the subdomain. Read more on Coolify domain setup here: https://coolify.io/docs/knowledge-base/dns-configuration
- Create a new project or use the default one
- Create a new resource, select
PostgreSQL- I pick the default PostgreSQL 16 variant, you can try others as well - they should work just fine
- Name it
db(to keep things clean) - Click
Startto set up the database - Copy the
Postgres URL (internal)- we'll need it later
- Create a new resource, select
Docker ImageunderDocker Based- We'll write
ghcr.io/<your-github-username>/<something>as the Docker image name since we'll be using the Github Container Registry (ghcr.io) to store our Docker images - I'll write
ghcr.io/infomiho/pokemon-serverfor my server image (I'll usepokemon-serveras my app name later in the Github Action) - Name the app
serverto keep things clean - Set the
Domainstohttps://api.<your-domain> - Set the
Docker Image Tagtomainsince we'll use that tag later - Set the
Port Exposesto3001 - Make sure to hit the
Savebutton after you change stuff
- We'll write
- Create a new resource, select
Docker ImageunderDocker Based- I'll write
ghcr.io/infomiho/pokemon-clientfor my client image (I'll usepokemon-clientas my app name later in the Github Action) - Name the app
clientto keep things clean - Set the
Domainstohttps://<your-domain> - Set the
Docker Image Tagtomainsince we'll use that tag later - Set the
Port Exposesto8043 - Make sure to hit the
Savebutton after you change stuff
- I'll write
Let's go back into the server app and configure the required env vars:
- Go under
Environment Variables - Add the following env vars:
DATABASE_URLwith value of thePostgres URL (internal)JWT_SECRETgenerate it with some online generatorPORTset it to3001WASP_WEB_CLIENT_URLset it tohttps://<your-domain>WASP_SERVER_URLset it tohttps://api.<your-domain>
- Add any other env vars you might have defined locally in the
.env.serverfile
- In your app root dir create a new
.githubfolder - Inside of
.githubfolder, create a newworkflowsfolder - Copy the
deploy.ymlfile from this gist to theworkflowsfolder
Once you copy the deploy.yml, make sure to modify the:
WASP_VERSIONenv varSERVER_APP_NAMEenv var - this will be used in the Docker image nameSERVER_APP_URLenv varCLIENT_APP_NAMEenv var - this will be used in the Docker image name
The DOCKER_REGISTRY, DOCKER_REGISTRY_USERNAME and DOCKER_REGISTRY_PASSWORD env vars will work out of the box for Github Container Registry.
Warning
If your app is located in the app folder (e.g. Open Saas has the app in the app folder) you can use the action as-is.
If your app is not in the app folder, follow the comments to modify some paths.
The Github Action depends on some repository secrets to work properly - these are some values that can't be public. You add them by going into your repository Settings and then find Secrets and variables and select Actions.
Let's add the:
SERVER_COOLIFY_WEBHOOKsecret- Go to your
serverapp - Click
Webhooksand copy theDeploy Webhook - Paste it as the secret value
- Go to your
CLIENT_COOLIFY_WEBHOOKsecret- Go to your
clientapp - Click
Webhooksand copy theDeploy Webhook - Paste it as the secret value
- Go to your
COOLIFY_TOKENsecret- Go to
Settingsand enable API - Go to
Keys & Tokensnext and clickAPI tokens - Create a new API token with
Root Access - Copy it and paste it under the secret value
- Go to
You can move your domain's nameservers to Cloudflare to get the benefits of their CDN and DDoS protections.
I've had to set my SSL mode to Full to get it working.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: "Deploy" | |
| on: | |
| push: | |
| branches: | |
| - "main" | |
| # This will make sure that only one deployment is running at a time | |
| concurrency: | |
| group: deployment | |
| cancel-in-progress: true | |
| env: | |
| WASP_VERSION: "0.17.0" | |
| # Put your server app name here | |
| SERVER_APP_NAME: "pokemon-server" | |
| # After you know the server URL, put the URL here | |
| SERVER_APP_URL: "https://api.<your-domain>" | |
| # Put your client app name here | |
| CLIENT_APP_NAME: "pokemon-client" | |
| DOCKER_REGISTRY: "ghcr.io" | |
| DOCKER_REGISTRY_USERNAME: ${{ github.repository_owner }} | |
| # This secret is provided by GitHub by default and is used to authenticate with the Container registry | |
| DOCKER_REGISTRY_PASSWORD: ${{ secrets.GITHUB_TOKEN }} | |
| jobs: | |
| build-and-push-images: | |
| permissions: | |
| contents: read | |
| packages: write | |
| runs-on: ubuntu-latest | |
| # REMOVE this whole block if your app is not in the `app` folder | |
| defaults: | |
| run: | |
| working-directory: ./app | |
| steps: | |
| - name: Checkout repository | |
| uses: actions/checkout@v4 | |
| - name: Log in to the Container registry | |
| uses: docker/login-action@v3 | |
| with: | |
| registry: ghcr.io | |
| username: ${{ env.DOCKER_REGISTRY_USERNAME }} | |
| password: ${{ env.DOCKER_REGISTRY_PASSWORD }} | |
| - name: (server) Extract metadata for Docker | |
| id: meta-server | |
| uses: docker/metadata-action@v5 | |
| with: | |
| images: ${{ env.DOCKER_REGISTRY }}/${{ env.DOCKER_REGISTRY_USERNAME }}/${{ env.SERVER_APP_NAME }} | |
| - name: (client) Extract metadata for Docker | |
| id: meta-client | |
| uses: docker/metadata-action@v5 | |
| with: | |
| images: ${{ env.DOCKER_REGISTRY }}/${{ env.DOCKER_REGISTRY_USERNAME }}/${{ env.CLIENT_APP_NAME }} | |
| - name: Install Wasp | |
| shell: bash | |
| run: curl -sSL https://get.wasp.sh/installer.sh | sh -s -- -v ${{ env.WASP_VERSION }} | |
| # Insert this block if you are using Wasp TS Spec | |
| #- name: Initialize Wasp TS Spec | |
| # shell: bash | |
| # run: wasp ts-setup | |
| - name: Build Wasp app | |
| shell: bash | |
| run: wasp build | |
| - name: (client) Build | |
| shell: bash | |
| run: | | |
| cd ./.wasp/build/web-app | |
| REACT_APP_API_URL=${{ env.SERVER_APP_URL }} npm run build | |
| - name: (client) Prepare the Dockerfile | |
| shell: bash | |
| run: | | |
| cd ./.wasp/build/web-app | |
| echo "FROM pierrezemb/gostatic" > Dockerfile | |
| echo "CMD [\"-fallback\", \"index.html\", \"-enable-logging\"]" >> Dockerfile | |
| echo "COPY ./build /srv/http" >> Dockerfile | |
| - name: (server) Build and push Docker image | |
| uses: docker/build-push-action@v6 | |
| with: | |
| # REMOVE the `app` bit from the path if your app is not in the `app` folder | |
| context: ./app/.wasp/build | |
| # REMOVE the `app` bit from the path if your app is not in the `app` folder | |
| file: ./app/.wasp/build/Dockerfile | |
| push: true | |
| tags: ${{ steps.meta-server.outputs.tags }} | |
| labels: ${{ steps.meta-server.outputs.labels }} | |
| - name: (client) Build and push Docker image | |
| uses: docker/build-push-action@v6 | |
| with: | |
| # REMOVE the `app` bit from the path if your app is not in the `app` folde | |
| context: ./app/.wasp/build/web-app | |
| # REMOVE the `app` bit from the path if your app is not in the `app` folder | |
| file: ./app/.wasp/build/web-app/Dockerfile | |
| push: true | |
| tags: ${{ steps.meta-client.outputs.tags }} | |
| labels: ${{ steps.meta-client.outputs.labels }} | |
| # You can get the webhook URLs from the Coolify dashboard | |
| # Put them in the repository secrets under CLIENT_COOLIFY_WEBHOOK and SERVER_COOLIFY_WEBHOOK | |
| - name: Trigger Deploy Webhooks | |
| env: | |
| CLIENT_COOLIFY_WEBHOOK: ${{ secrets.CLIENT_COOLIFY_WEBHOOK }} | |
| SERVER_COOLIFY_WEBHOOK: ${{ secrets.SERVER_COOLIFY_WEBHOOK }} | |
| COOLIFY_TOKEN: ${{ secrets.COOLIFY_TOKEN }} | |
| run: | | |
| curl "${{ env.CLIENT_COOLIFY_WEBHOOK }}" --header 'Authorization: Bearer ${{ env.COOLIFY_TOKEN }}' | |
| curl "${{ env.SERVER_COOLIFY_WEBHOOK }}" --header 'Authorization: Bearer ${{ env.COOLIFY_TOKEN }}' |
Author
Huh, I don't have a settings
That could be it, I was having trouble setting that up (GH wasn't letting me add the app to my org, even though I owned it 🤷 ) so I had to authenticate manually.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the update! I'll update the gist :)
ghcr.ioimage pulling will work without the explicit login if you connect your Coolify instance with a Github App in theSourcessection in Coolify. For me it just worked out of the box with a private repository when I did that step.