coolify-operator
FeaturedMaster Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or official CLI.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- fabricioctelles
- Repository
- fabricioctelles/skills
- Created
- 7 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
coolify-cli
Operate Coolify instances through the official coollabsio/coolify-cli. Use for CLI setup and authentication, resource inspection, deployments, logs, application configuration, environment variables, databases, services, backups, and infrastructure management in Coolify.
coolify-manager
Manage and troubleshoot Coolify deployments using the official CLI (v1.4.0) and API. Use this skill when the user needs help with Coolify server management, WordPress troubleshooting on Coolify, debugging service issues, checking SSL certificates, accessing containers, managing applications and databases, deploying code, creating services or databases, managing environment variables, configuring backups with S3 and retention policies, or performing any deployment operations through Coolify. Also use when the user mentions docker containers on Coolify, deploy failures, self-hosted infrastructure management, or needs to batch-deploy multiple resources at once. Particularly useful for diagnosing down services, fixing .htaccess issues, REST API problems, and managing one-click services like WordPress, Ghost, n8n, Supabase, Uptime Kuma.
coolify
Use when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is `railway`), NOT sizing/hardening the box (that is `hetzner`), NOT authoring Dockerfiles (that is `docker`).