Deploy with Nixpacks

Use this guide to connect a Git repository, let Nixpacks detect the application, and deploy the generated image with Coolify.

Read the Nixpacks overview first when you need to decide whether automatic detection fits the codebase.

Deploy the application

Create a resource

Open the target project and environment, then select + New.

Create New Resource button in a Coolify project

Connect the repository

Create an application from a public repository, deploy key, or supported Git App.

Git repository source options for a Nixpacks application

For a public repository, paste its HTTPS URL and select Check Repository.

Public repository URL field for a Nixpacks application

Select the repository and branch.

Select Nixpacks

Choose Nixpacks in Build pack during creation. After creation, this choice is Build strategy under General > Build pipeline.

Nixpacks option in the Build Pack selector

Set Base Directory to the directory Nixpacks should inspect. Use / for the repository root or a path such as /apps/api for an application in a monorepo.

Choose the application type

After creation, use General > Build pipeline > Site type to choose Dynamic, Static, or SPA (single-page application).

For static output:

choose Static site in Output type during creation
enter Publish Directory, such as /dist
keep the generated Nginx port 80

Static site settings for a Nixpacks application

For a server application:

choose Web application in Output type during creation
enter the internal port where the process listens

Server application settings for a Nixpacks build

Add environment variables

Continue to the application and open Environment Variables.

Add the values required by the application. Choose Available during build in Build time for values that the build command must read.

Environment Variables page for a Nixpacks application

Review the detected commands

Open General and review the detected Install Command, Build Command, and Start Command.

Override a command only when detection is incorrect or the codebase requires a custom command.

Install, build, and start command fields for a Nixpacks application

Deploy and verify

Configure a domain when the application should be public, then select Deploy.

Inspect the deployment log to confirm which providers, packages, and commands Nixpacks selected.

For a server application, open the application logs and confirm the process listens on the configured internal port. For a static application, open the domain and verify the generated assets and a client-side route.

Configure static output

Coolify uses Nginx to serve a static Nixpacks build.

Nginx selected for a static Nixpacks application

Use General > Build pipeline > Custom Nginx configuration only when the site needs behavior such as single-page application fallback, custom headers, or caching rules.

Generate button and Nginx configuration editor for a static Nixpacks application

Save the change and redeploy the application. Coolify copies the Nginx configuration into the final static image during the image build, so a restart that reuses the existing image cannot apply the change.

On this page