coolify-python-deploy_skill

Overview

This skill guides you step-by-step to deploy Python projects from GitHub to Coolify using Nixpacks or a Dockerfile. It focuses on practical setup: connecting the repo, selecting the build method, configuring ports and environment variables, and common troubleshooting tips. The goal is a reliable, repeatable deployment process for typical Python web apps.

How this skill works

The skill explains how Coolify detects and builds Python apps with Nixpacks by reading common dependency files (requirements.txt, pyproject.toml, setup.py). It also covers using a Dockerfile when you need full control over the build environment. Instructions include linking your GitHub repo, selecting the build pack, setting the start command and network port, and managing environment variables in Coolify.

When to use it

• Deploy a standard Python web app (Flask, FastAPI, Django) quickly with minimal config.
• You need automatic dependency detection and a simple build flow — use Nixpacks.
• Your app requires specific system packages or a custom image — use a Dockerfile.
• You want to manage secrets and environment variables centrally in Coolify.
• You are deploying from a GitHub repository and want continuous rebuilds on pushes.

Best practices

• Prefer Nixpacks for most Python projects to leverage automatic detection and reproducible builds.
• Always set the app listening port in Coolify to match the container start command (use $PORT where supported).
• Keep dependency files at the repository root: requirements.txt, pyproject.toml, or setup.py.
• Mark secrets as secret in Coolify and avoid committing .env files to GitHub.
• For complex dependencies, include system package installation in your Dockerfile or ensure Nixpacks can detect them.

Example use cases

• Deploy a FastAPI app using Nixpacks and a start command like: uvicorn main:app --host 0.0.0.0 --port $PORT.
• Deploy a Django site by providing requirements.txt and setting DJANGO_SETTINGS_MODULE and port in environment variables.
• Use a Dockerfile to include apt-get installs (libpq-dev, build-essential) for native Python dependencies.
• Connect a GitHub repo so pushes trigger rebuilds and deployments in Coolify.
• Switch between Nixpacks and Dockerfile build packs depending on simplicity versus custom requirements.