coolify-manager by ajmcclary/coolify-manager
npx skills add https://github.com/ajmcclary/coolify-manager --skill coolify-manager此技能支持通过官方 CLI 和直接 API 访问来管理 Coolify 部署。它提供了用于诊断服务问题、修复常见 WordPress 问题、管理容器以及在自托管和云端 Coolify 实例上执行部署操作的工作流。
在继续之前,请验证:
/security/api-tokens 处获取 API 令牌当用户出现以下情况时,调用此技能:
如果尚未安装 CLI,请使用捆绑的安装脚本:
bash scripts/install_coolify_cli.sh
这将安装到 ~/.local/bin/coolify。确保此目录在用户的 PATH 中:
export PATH="$HOME/.local/bin:$PATH"
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
将此行添加到用户的 shell 配置文件(~/.bashrc、~/.zshrc 等)中以实现持久化。
添加用户的 Coolify 实例:
coolify context add <context-name> <coolify-url> <api-token>
示例:
coolify context add production https://coolify.example.com YOUR_API_TOKEN
coolify context verify
这将确认身份验证和连接是否成功。
运行捆绑的健康检查脚本:
bash scripts/check_health.sh
这将显示:
当用户报告问题时:
是服务可用性问题吗?
是 WordPress 特定问题吗?
是性能/配置问题吗?
# 列出所有资源及其状态
coolify resource list
# 获取详细的服务信息
coolify service get SERVICE_UUID
# 检查特定应用程序
coolify app get APP_UUID
状态指示器:
running:healthy - 服务正常运行running:unhealthy - 服务存在问题(检查日志)stopped - 服务未运行deploying - 部署正在进行中# 应用程序日志
coolify app logs APP_UUID
# 获取更多行
coolify app logs APP_UUID --lines 500
对于具有多个组件的服务(例如带有数据库的 WordPress),首先获取服务详细信息以识别组件 UUID:
coolify service get SERVICE_UUID --format json
然后从 JSON 输出中提取应用程序/数据库 UUID。
当 CLI 不提供所需功能时,使用直接 API 调用。参考:references/api_endpoints.md
示例 - 获取详细的服务配置:
curl -H "Authorization: Bearer API_TOKEN" \
https://coolify-instance.com/api/v1/services/SERVICE_UUID
# 服务
coolify service start SERVICE_UUID
coolify service stop SERVICE_UUID
coolify service restart SERVICE_UUID
# 应用程序
coolify app start APP_UUID
coolify app stop APP_UUID
coolify app restart APP_UUID
# 数据库
coolify database start DB_UUID
coolify database stop DB_UUID
coolify database restart DB_UUID
# 通过 UUID 部署
coolify deploy APP_UUID
# 检查部署状态
coolify deploy list APP_UUID
# 列出环境变量
coolify app env list APP_UUID
# 添加/更新环境变量
coolify app env set APP_UUID VAR_NAME "value"
# 删除环境变量
coolify app env delete APP_UUID VAR_NAME
# 重启以应用更改
coolify app restart APP_UUID
对于 WordPress 特定问题,请参考:references/wordpress_fixes.md
通过 Coolify Web 终端(推荐):
通过 Docker(如果 SSH 访问可用):
docker exec -it CONTAINER_NAME bash
WordPress 文件位于:/var/www/html/
这是一个需要立即采取行动的关键问题:
访问容器终端(见上文)
检查 .htaccess 文件:
cd /var/www/html
cat .htaccess
识别有问题的行(通常是最后添加的行)
删除有问题的行:
sed -i '$d' /var/www/html/.htaccess
服务应立即恢复
要增加 PHP 限制(max_input_vars、上传限制等):
正确语法(不要使用 = 号,使用空格):
echo "php_value max_input_vars 3000" >> /var/www/html/.htaccess
echo "php_value upload_max_filesize 64M" >> /var/www/html/.htaccess
echo "php_value post_max_size 128M" >> /var/www/html/.htaccess
echo "php_value memory_limit 256M" >> /var/www/html/.htaccess
验证:
tail -5 /var/www/html/.htaccess
如果站点健康报告 REST API 不可用但站点工作正常:
从外部测试 REST API:
curl https://site.com/wp-json/
如果返回 JSON,则为误报 - API 工作正常
常见原因:站点健康回环测试被阻止,而非实际 API
验证 .htaccess 中的 HTTP_AUTHORIZATION:
grep "HTTP_AUTHORIZATION" /var/www/html/.htaccess
应包含:
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
有关详细的 WordPress 故障排除步骤,请将 references/wordpress_fixes.md 加载到上下文中。
检查证书状态:
echo | openssl s_client -servername domain.com -connect domain.com:443 2>/dev/null | openssl x509 -noout -dates -subject -issuer
Coolify 使用 Traefik 和 Let's Encrypt 实现自动 SSL。证书在到期前会自动续订。
如果证书无效:
在 Coolify 实例之间切换:
# 列出上下文
coolify context list
# 切换上下文
coolify context use staging
# 执行操作
coolify deploy APP_UUID
# 切换回来
coolify context use production
将 --format json 与 jq 等工具结合使用:
# 获取所有不健康的服务
coolify resource list --format json | jq '.[] | select(.status | contains("unhealthy"))'
# 获取所有正在运行的应用程序
coolify resource list --format json | jq '.[] | select(.type=="application" and .status=="running")'
# 提取服务 UUID
coolify service list --format json | jq -r '.[].uuid'
# 列出带有 IP/端口的服务器
coolify server list -s
# 验证服务器连接
coolify server validate SERVER_UUID
# 获取服务器域名
coolify server domains SERVER_UUID
# 列出数据库
coolify database list
# 备份数据库
coolify database backup DB_UUID
# 列出备份
coolify database backups DB_UUID
此技能包含全面的参考文档:
当用户需要详细的 CLI 命令语法、标志或示例时,加载 references/cli_commands.md。
当执行直接 API 调用或 CLI 不支持所需操作时,加载 references/api_endpoints.md。
当排除 WordPress 特定问题(如 .htaccess 问题、PHP 配置、REST API 问题或 SSL 证书)时,加载 references/wordpress_fixes.md。
coolify resource listcoolify service get UUIDcoolify app logs APP_UUIDcoolify resource list/var/www/html.htaccess 是否存在语法错误curl https://site.com/wp-json/coolify deploy list APP_UUIDcoolify deploy get DEPLOY_UUIDcoolify app logs APP_UUIDcoolify deploy APP_UUID确保 ~/.local/bin 在 PATH 中:
echo $PATH | grep ".local/bin"
如果未找到:
export PATH="$HOME/.local/bin:$PATH"
添加到 shell 配置中以实现持久化。
验证 API 令牌是否有效(检查 Coolify 仪表板)
检查 Coolify 实例 URL 是否正确
测试手动连接:
curl -H "Authorization: Bearer TOKEN" https://instance.com/api/v1/version
如果需要,重新配置上下文
确保 API 令牌具有所需权限:
在 Coolify 仪表板的 /security/api-tokens 处检查令牌权限。
每周安装次数
88
仓库
GitHub 星标数
2
首次出现
2026年1月26日
安全审计
安装于
opencode85
github-copilot78
gemini-cli77
codex77
kimi-cli68
amp67
This skill enables management of Coolify deployments through both the official CLI and direct API access. It provides workflows for diagnosing service issues, fixing common WordPress problems, managing containers, and performing deployment operations across self-hosted and cloud Coolify instances.
Before proceeding, verify:
/security/api-tokensInvoke this skill when the user:
If the CLI is not already installed, use the bundled installation script:
bash scripts/install_coolify_cli.sh
This installs to ~/.local/bin/coolify. Ensure this directory is in the user's PATH:
export PATH="$HOME/.local/bin:$PATH"
Add this line to the user's shell configuration file (~/.bashrc, ~/.zshrc, etc.) for persistence.
Add the user's Coolify instance:
coolify context add <context-name> <coolify-url> <api-token>
Example:
coolify context add production https://coolify.example.com YOUR_API_TOKEN
coolify context verify
This confirms successful authentication and connectivity.
Run the bundled health check script:
bash scripts/check_health.sh
This displays:
When a user reports an issue:
Is it service availability?
Is it WordPress-specific?
Is it performance/configuration?
# List all resources with status
coolify resource list
# Get detailed service info
coolify service get SERVICE_UUID
# Check specific application
coolify app get APP_UUID
Status indicators:
running:healthy - Service is operationalrunning:unhealthy - Service has issues (check logs)stopped - Service is not runningdeploying - Deployment in progress# Application logs
coolify app logs APP_UUID
# Get more lines
coolify app logs APP_UUID --lines 500
For services with multiple components (like WordPress with database), get the service details first to identify component UUIDs:
coolify service get SERVICE_UUID --format json
Then extract application/database UUIDs from the JSON output.
When CLI doesn't provide needed functionality, use direct API calls. Reference: references/api_endpoints.md
Example - Get detailed service configuration:
curl -H "Authorization: Bearer API_TOKEN" \
https://coolify-instance.com/api/v1/services/SERVICE_UUID
# Services
coolify service start SERVICE_UUID
coolify service stop SERVICE_UUID
coolify service restart SERVICE_UUID
# Applications
coolify app start APP_UUID
coolify app stop APP_UUID
coolify app restart APP_UUID
# Databases
coolify database start DB_UUID
coolify database stop DB_UUID
coolify database restart DB_UUID
# Deploy by UUID
coolify deploy APP_UUID
# Check deployment status
coolify deploy list APP_UUID
# List env vars
coolify app env list APP_UUID
# Add/update env var
coolify app env set APP_UUID VAR_NAME "value"
# Delete env var
coolify app env delete APP_UUID VAR_NAME
# Restart to apply changes
coolify app restart APP_UUID
For WordPress-specific issues, reference: references/wordpress_fixes.md
Via Coolify Web Terminal (Recommended):
Via Docker (if SSH access available):
docker exec -it CONTAINER_NAME bash
WordPress files are located at: /var/www/html/
This is a critical issue that requires immediate action:
Access the container terminal (see above)
Check the .htaccess file:
cd /var/www/html
cat .htaccess
Identify problematic line (usually last added line)
Remove problematic line:
sed -i '$d' /var/www/html/.htaccess
Service should recover immediately
To increase PHP limits (max_input_vars, upload limits, etc.):
Correct syntax (no = sign, use space):
echo "php_value max_input_vars 3000" >> /var/www/html/.htaccess
echo "php_value upload_max_filesize 64M" >> /var/www/html/.htaccess
echo "php_value post_max_size 128M" >> /var/www/html/.htaccess
echo "php_value memory_limit 256M" >> /var/www/html/.htaccess
Verify:
tail -5 /var/www/html/.htaccess
If Site Health reports REST API unavailable but the site works normally:
Test REST API externally:
curl https://site.com/wp-json/
If JSON returns, it's a false positive - the API works fine
Common cause: Site Health loopback test is blocked, not the actual API
Verify HTTP_AUTHORIZATION in .htaccess:
grep "HTTP_AUTHORIZATION" /var/www/html/.htaccess
Should contain:
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
For detailed WordPress troubleshooting steps, load references/wordpress_fixes.md into context.
Check certificate status:
echo | openssl s_client -servername domain.com -connect domain.com:443 2>/dev/null | openssl x509 -noout -dates -subject -issuer
Coolify uses Traefik with Let's Encrypt for automatic SSL. Certificates auto-renew before expiration.
If certificate is invalid:
Switch between Coolify instances:
# List contexts
coolify context list
# Switch context
coolify context use staging
# Perform operations
coolify deploy APP_UUID
# Switch back
coolify context use production
Use --format json with tools like jq:
# Get all unhealthy services
coolify resource list --format json | jq '.[] | select(.status | contains("unhealthy"))'
# Get all running applications
coolify resource list --format json | jq '.[] | select(.type=="application" and .status=="running")'
# Extract service UUIDs
coolify service list --format json | jq -r '.[].uuid'
# List servers with IPs/ports
coolify server list -s
# Validate server connection
coolify server validate SERVER_UUID
# Get server domains
coolify server domains SERVER_UUID
# List databases
coolify database list
# Backup database
coolify database backup DB_UUID
# List backups
coolify database backups DB_UUID
This skill includes comprehensive reference documentation:
Load references/cli_commands.md when the user needs detailed CLI command syntax, flags, or examples.
Load references/api_endpoints.md when performing direct API calls or when CLI doesn't support the needed operation.
Load references/wordpress_fixes.md when troubleshooting WordPress-specific issues like .htaccess problems, PHP configuration, REST API issues, or SSL certificates.
coolify resource listcoolify service get UUIDcoolify app logs APP_UUIDcoolify resource list/var/www/html.htaccess for syntax errorscurl https://site.com/wp-json/coolify deploy list APP_UUIDcoolify deploy get DEPLOY_UUIDcoolify app logs APP_UUIDcoolify deploy APP_UUIDEnsure ~/.local/bin is in PATH:
echo $PATH | grep ".local/bin"
If not found:
export PATH="$HOME/.local/bin:$PATH"
Add to shell config for persistence.
Verify API token is valid (check Coolify dashboard)
Check Coolify instance URL is correct
Test manual connection:
curl -H "Authorization: Bearer TOKEN" https://instance.com/api/v1/version
Re-configure context if needed
Ensure API token has required permissions:
Check token permissions in Coolify dashboard at /security/api-tokens.
Weekly Installs
88
Repository
GitHub Stars
2
First Seen
Jan 26, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykFail
Installed on
opencode85
github-copilot78
gemini-cli77
codex77
kimi-cli68
amp67
Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU
94,100 周安装