ajmcclary/coolify-manager
Overview
This skill manages and troubleshoots Coolify deployments using the official CLI and direct API calls. It provides clear workflows to diagnose down services, fix WordPress issues, check SSL certificates, access containers, and perform deployment and environment operations across self-hosted or cloud Coolify instances.
How this skill works
The skill uses the Coolify CLI for common actions (context management, service control, logs, deploys) and falls back to direct API requests when finer control or additional metadata is needed. It guides through a decision tree: check service status, inspect logs, access containers for file fixes (like .htaccess), update env vars or PHP settings, and re-deploy or restart services as required.
When to use it
- Site or service hosted on Coolify is down or unhealthy
- WordPress shows 500 errors, REST API warnings, or .htaccess problems
- You need container terminal access to inspect files or run fixes
- SSL certificate problems or Traefik/Let’s Encrypt issues
- To list, start/stop/restart services, deploy apps, or manage env vars
- When CLI lacks needed functionality and direct API calls are required
Best practices
- Install and verify the Coolify CLI, add contexts and confirm connectivity before changes
- Always check service status and logs first to narrow root cause
- Use container terminal for file-level fixes (e.g., .htaccess) and validate changes before restarting
- Manage environment variables via CLI and restart the app to apply them
- Use --format json with jq for batch queries and extracting UUIDs
- Ensure API tokens have appropriate permissions and keep them scoped
Example use cases
- Diagnose a down WordPress site: check resource list, inspect app logs, open container, revert a bad .htaccess line, restart service
- Fix REST API false positives: curl the wp-json endpoint, verify HTTP_AUTHORIZATION rewrite in .htaccess
- Recover a failed deployment: list recent deploys, get deploy details, inspect logs, update env vars or code, trigger a new deploy
- Resolve SSL issues: inspect certificate via openssl, regenerate cert in Coolify dashboard, verify Traefik labels
- Perform bulk checks: use coolify resource list --format json | jq to find unhealthy services across contexts
FAQ
Run coolify context add <name> <url> <api-token>, then coolify context verify to confirm connectivity.
What if the CLI doesn’t expose a needed operation?
Use the Coolify API with curl and an API token to call endpoints directly for detailed service or configuration data.