coolify:provision
php artisan coolify:provisionInteractive prompts guide server, project, and repository selection.
Options
Section titled “Options”--name= # Application name--domain= # Application domain--server= # Server UUID--project= # Project UUID--environment= # Environment (default: production)--repository= # GitHub repository (owner/repo)--branch= # Git branch--with-postgres # Create PostgreSQL database--with-dragonfly # Create Dragonfly instance--with-redis # Create Redis instance--all # Create app with Postgres and Dragonfly--deploy # Trigger deployment after provisioning--force # Skip confirmationsNon-Interactive
Section titled “Non-Interactive”php artisan coolify:provision \ --server=abc123 \ --name="My App" \ --repository=owner/repo \ --branch=main \ --all \ --deploy \ --forceWhat Gets Created
Section titled “What Gets Created”- Project (if needed)
- Environment within project
- Application with Dockerfile configuration
- PostgreSQL database (with
--with-postgresor--all) - Dragonfly cache (with
--with-dragonflyor--all) - Environment variables linking all services
Database Storage
Section titled “Database Storage”Resource UUIDs are stored in the coolify_resources table:
| Column | Value |
|---|---|
name | Application name |
server_uuid | Selected server |
project_uuid | Project UUID |
environment | Environment name |
application_uuid | Created application |
database_uuid | PostgreSQL UUID |
redis_uuid | Dragonfly/Redis UUID |
deploy_key_uuid | SSH key UUID |
repository | GitHub repository |
branch | Git branch |
is_default | true |
This record is marked as the default, so subsequent commands (coolify:deploy, coolify:status, etc.) use it automatically.
Generated Files
Section titled “Generated Files”Creates in your project:
Dockerfiledocker/├── nginx.conf├── php.ini└── supervisord.conf