Coolify Manager 技能：管理 Coolify 部署，诊断 WordPress 问题，自动化运维

coolify-manager by ajmcclary/coolify-manager

135 周安装量

3 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/ajmcclary/coolify-manager --skill coolify-manager

开发运维命令行工具 WordPress

🇨🇳中文介绍

Coolify Manager

概述

此技能支持通过官方 CLI 和直接 API 访问来管理 Coolify 部署。它提供了用于诊断服务问题、修复常见 WordPress 问题、管理容器以及在自托管和云端 Coolify 实例上执行部署操作的工作流。

快速开始

先决条件检查

在继续之前，请验证：

用户有权访问 Coolify 实例（自托管或云端）
用户可以从其 Coolify 仪表板的 /security/api-tokens 处获取 API 令牌
用户知道其 Coolify 实例的 URL

何时使用此技能

当用户出现以下情况时，调用此技能：

提及 Coolify 名称
需要调试托管在 Coolify 上宕机的 WordPress 站点
想要检查服务健康状况、日志或状态
需要访问容器终端
想要管理部署、服务或应用程序
在 Coolify 托管的站点上遇到 SSL 证书问题
需要修复 .htaccess 或 PHP 配置问题
想要管理环境变量或配置

安装与设置

步骤 1：安装 Coolify CLI

如果尚未安装 CLI，请使用捆绑的安装脚本：

bash scripts/install_coolify_cli.sh

这将安装到 ~/.local/bin/coolify。确保此目录在用户的 PATH 中：

export PATH="$HOME/.local/bin:$PATH"

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 2：配置上下文

添加用户的 Coolify 实例：

coolify context add <context-name> <coolify-url> <api-token>

coolify context add production https://coolify.example.com YOUR_API_TOKEN

步骤 3：验证连接

coolify context verify

这将确认身份验证和连接是否成功。

运行捆绑的健康检查脚本：

bash scripts/check_health.sh

CLI 版本
已配置的上下文
连接状态
可用资源
服务器状态

当用户报告问题时：

是服务可用性问题吗？
- 站点宕机 → 检查服务状态
- 容器无响应 → 检查日志
- 部署失败 → 检查部署历史
是 WordPress 特定问题吗？
- 更改 .htaccess 后出现 500 错误 → 修复 .htaccess
- REST API 警告 → 诊断 REST API
- PHP 限制 → 更新 PHP 配置
- SSL 问题 → 检查证书
是性能/配置问题吗？
- 需要更改环境变量 → 管理环境
- 需要扩展 → 管理资源
- 需要部署 → 触发部署

# 列出所有资源及其状态
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 故障排除

对于 WordPress 特定问题，请参考：references/wordpress_fixes.md

访问 WordPress 容器

通过 Coolify Web 终端（推荐）：

导航到 Coolify 仪表板
转到 WordPress 服务
点击侧边栏中的“终端”
选择“wordpress”容器

通过 Docker（如果 SSH 访问可用）：

docker exec -it CONTAINER_NAME bash

WordPress 文件位于：/var/www/html/

常见 WordPress 问题

编辑 .htaccess 后站点宕机

这是一个需要立即采取行动的关键问题：

访问容器终端（见上文）
检查 .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 仪表板 → 服务 → 域名
重新生成 SSL 证书
验证服务配置中的 Traefik 标签

使用多个上下文

在 Coolify 实例之间切换：

# 列出上下文
coolify context list

# 切换上下文
coolify context use staging

# 执行操作
coolify deploy APP_UUID

# 切换回来
coolify context use production

使用 JSON 输出进行批量操作

将 --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 修复参考

当排除 WordPress 特定问题（如 .htaccess 问题、PHP 配置、REST API 问题或 SSL 证书）时，加载 references/wordpress_fixes.md。

模式：服务宕机

检查状态：coolify resource list
获取详细信息：coolify service get UUID
检查日志：coolify app logs APP_UUID
从日志中识别问题
修复（重启、更新配置、修复文件）
验证：coolify resource list

模式：WordPress 站点问题

访问容器终端（通过 Coolify 仪表板）
导航到 /var/www/html
检查 .htaccess 是否存在语法错误
测试 REST API：curl https://site.com/wp-json/
如果需要，检查 PHP 配置
如果进行了更改，则重启服务

模式：部署问题

列出最近的部署：coolify deploy list APP_UUID
获取部署详细信息：coolify deploy get DEPLOY_UUID
检查应用程序日志：coolify app logs APP_UUID
修复已识别的问题（环境变量、配置、代码）
触发新部署：coolify 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 处检查令牌权限。

🇺🇸English

Coolify Manager

Overview

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.

Quick Start

Prerequisites Check

Before proceeding, verify:

User has access to a Coolify instance (self-hosted or cloud)
User can obtain an API token from their Coolify dashboard at /security/api-tokens
User knows their Coolify instance URL

When to Use This Skill

Invoke this skill when the user:

Mentions Coolify by name
Needs to debug a down WordPress site hosted on Coolify
Wants to check service health, logs, or status
Needs to access a container terminal
Wants to manage deployments, services, or applications
Has SSL certificate issues on Coolify-hosted sites
Needs to fix .htaccess or PHP configuration issues
Wants to manage environment variables or configurations

Installation & Setup

Step 1: Install Coolify CLI

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.

Step 2: Configure Context

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

Step 3: Verify Connection

coolify context verify

This confirms successful authentication and connectivity.

Health Check

Run the bundled health check script:

bash scripts/check_health.sh

This displays:

CLI version
Configured contexts
Connection status
Available resources
Server status

Diagnosing Issues

Workflow Decision Tree

When a user reports an issue:

Is it service availability?
- Site is down → Check service status
- Container not responding → Check logs
- Deploy failed → Check deployment history
Is it WordPress-specific?
- 500 error after .htaccess change → Fix .htaccess
- REST API warnings → Diagnose REST API
- PHP limits → Update PHP configuration
- SSL issues → Check certificates
Is it performance/configuration?
- Need to change env vars → Manage environment
- Need to scale → Manage resources
- Need to deploy → Trigger deployment

Check Service Status

# 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 operational
running:unhealthy - Service has issues (check logs)
stopped - Service is not running
deploying - Deployment in progress

Check Logs

# 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.

Using the API Directly

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

Managing Services

Start/Stop/Restart

# 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 Applications

# Deploy by UUID
coolify deploy APP_UUID

# Check deployment status
coolify deploy list APP_UUID

Manage Environment Variables

# 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

WordPress Troubleshooting

For WordPress-specific issues, reference: references/wordpress_fixes.md

Accessing WordPress Container

Via Coolify Web Terminal (Recommended):

Navigate to Coolify dashboard
Go to WordPress service
Click "Terminal" in sidebar
Select "wordpress" container

Via Docker (if SSH access available):

docker exec -it CONTAINER_NAME bash

WordPress files are located at: /var/www/html/

Common WordPress Issues

Site Down After .htaccess Edit

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

PHP Configuration Limits

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

REST API False Positives

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.

SSL Certificate Issues

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:

Check Coolify dashboard → Service → Domains
Regenerate SSL certificate
Verify Traefik labels in service configuration

Advanced Operations

Working with Multiple Contexts

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

Batch Operations with JSON Output

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'

Server Management

# 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

Backup and Recovery

# List databases
coolify database list

# Backup database
coolify database backup DB_UUID

# List backups
coolify database backups DB_UUID

References

This skill includes comprehensive reference documentation:

CLI Commands Reference

Load references/cli_commands.md when the user needs detailed CLI command syntax, flags, or examples.

API Endpoints Reference

Load references/api_endpoints.md when performing direct API calls or when CLI doesn't support the needed operation.

WordPress Fixes Reference

Load references/wordpress_fixes.md when troubleshooting WordPress-specific issues like .htaccess problems, PHP configuration, REST API issues, or SSL certificates.

Common Patterns

Pattern: Service is Down

Check status: coolify resource list
Get details: coolify service get UUID
Check logs: coolify app logs APP_UUID
Identify issue from logs
Fix (restart, update config, fix files)
Verify: coolify resource list

Pattern: WordPress Site Issues

Access container terminal (via Coolify dashboard)
Navigate to /var/www/html
Check .htaccess for syntax errors
Test REST API: curl https://site.com/wp-json/
Check PHP configuration if needed
Restart service if changes made

Pattern: Deployment Issues

List recent deployments: coolify deploy list APP_UUID
Get deployment details: coolify deploy get DEPLOY_UUID
Check application logs: coolify app logs APP_UUID
Fix identified issues (env vars, config, code)
Trigger new deployment: coolify deploy APP_UUID

Troubleshooting This Skill

CLI Not Found

Ensure ~/.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.

Connection Failures

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

Permission Issues

Ensure API token has required permissions:

Read access for status/logs
Write access for deployments/restarts
Deploy access for triggering deployments

Check token permissions in Coolify dashboard at /security/api-tokens.

Weekly Installs

Repository

ajmcclary/cooli…-manager

GitHub Stars

First Seen

Jan 26, 2026

Security Audits

Gen Agent Trust HubFail SocketPass SnykFail

Installed on

opencode85

github-copilot78

gemini-cli77

codex77

kimi-cli68

amp67

Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU

94,100 周安装

Coolify Manager 技能：管理 Coolify 部署，诊断 WordPress 问题，自动化运维

🇨🇳中文介绍

Coolify Manager

概述

快速开始

先决条件检查

何时使用此技能

安装与设置

步骤 1：安装 Coolify CLI

相关 Skills

步骤 2：配置上下文

步骤 3：验证连接

健康检查

诊断问题

工作流决策树

检查服务状态

检查日志

直接使用 API

管理服务

启动/停止/重启

部署应用程序

管理环境变量

WordPress 故障排除

访问 WordPress 容器

常见 WordPress 问题

编辑 .htaccess 后站点宕机

PHP 配置限制

REST API 误报

SSL 证书问题

高级操作

使用多个上下文

使用 JSON 输出进行批量操作

服务器管理

备份与恢复

参考

CLI 命令参考

API 端点参考

WordPress 修复参考

常见模式

模式：服务宕机

模式：WordPress 站点问题

模式：部署问题

此技能故障排除

找不到 CLI

连接失败

权限问题

🇺🇸English

Coolify Manager

Overview

Quick Start

Prerequisites Check

When to Use This Skill

Installation & Setup

Step 1: Install Coolify CLI

Step 2: Configure Context

Step 3: Verify Connection

Health Check

Diagnosing Issues

Workflow Decision Tree

Check Service Status

Check Logs

Using the API Directly

Managing Services

Start/Stop/Restart

Deploy Applications

Manage Environment Variables

WordPress Troubleshooting

Accessing WordPress Container

Common WordPress Issues

Site Down After .htaccess Edit

PHP Configuration Limits

REST API False Positives

SSL Certificate Issues

Advanced Operations

Working with Multiple Contexts

Batch Operations with JSON Output

Server Management

Backup and Recovery

References

CLI Commands Reference