Guide to HCS Deployment Options and Configurations

By default, the container won’t have any resource limits. You can set the limits here. For more details, read the Docker documentation.

Deployment Types

There are several types of application deployments available.

• Public Git Repository

• Private Git Repository (GitHub App)

• Private Git Repository (Deploy Key)

• Based on a Dockerfile

• Based on a Docker Compose

• Based on a Docker Image

Build Packs

These are the supported build packs:

• Nixpacks

• Dockerfile

• Docker Image

• Docker Compose

Nixpacks

Coolify uses Nixpacks as build pack by default. Nixpacks detect what kind of application are you trying to deploy and builds it accordingly.

But if needed, you can customize it by adding a nixpacks.toml file to your repository or setting the right environment variables.

For example, if you are using a NodeJS application, you can set the NIXPACKS_NODE_VERSION to control the NodeJS version.

Dockerfile

Dockerfile based build packs are useful if you have a custom dockerfile inside your Git repository.

Custom Dockerfile Location

You can always set your custom dockerfile location. By default, it is set to /Dockerfile.

Docker Image

You can deploy any docker images from any Docker compatible repository. For example, you can deploy images from Docker Hub, GitHub Container Registry, etc.

Docker Compose

Docker Compose based deployments are useful for complex applications. You can define multiple services in a single docker-compose.yml file and deploy them together.

• Languages/Frameworks

• Services