Build Process

Tapitalee can handle the container image build process on your behalf when you use tapit image build or tapit image deploy.

With Buildpacks

If there is no Dockerfile in the current directory, or you don’t specify one via the dockerfile= option, Tapitalee defaults to a buildpack build. This runs pack build using the pack tool and Cloud Native Buildpacks to automatically detect your application type and generate a container image — no Dockerfile required.

This is the easiest way to get started: just run tapit image deploy in your project directory.

$ tapit image deploy

Buildpacks support many common languages and frameworks out of the box, including Ruby, Node.js, Python, Go, and more.

With Dockerfile

For more control over the build process, you can provide your own Dockerfile. Place it in the project directory and Tapitalee will use it automatically, or specify a custom path with dockerfile=:

$ tapit image deploy dockerfile=./path/to/Dockerfile

Using a Dockerfile gives you full control over:

• The base image
• System dependencies
• Build steps and caching
• Runtime configuration

AI tools are great for help generating a Dockerfile tailored to your application if you’re not sure where to start.

For the full list of available options, see the CLI Reference.