服务器操作
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需手动接入
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- Docker
- 运行环境要求
- Docker
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 读取环境变量
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Cloudron Server Operations
The `cloudron` CLI manages apps on a Cloudron server. All commands operate on apps, not the server itself.
## Setup
```bash
sudo npm install -g cloudron # install on your PC/Mac, NOT on the server
cloudron login my.example.com # opens browser for authentication
```
Token is stored in `~/.cloudron.json`.
For self-signed certificates: `cloudron login my.example.com --allow-selfsigned`
## App targeting
Most commands require `--app` to specify which app:
```bash
cloudron logs --app blog.example.com # by FQDN
cloudron logs --app blog # by subdomain/location
cloudron logs --app 52aae895-5b7d-4625-8d4c-... # by app ID
```
When run from a directory with `CloudronManifest.json` and a previously installed app, the CLI auto-detects the app (stored as `appId` in the per-directory config).
## Commands
### Listing and inspection
```bash
cloudron list # all installed apps
cloudron list -q # quiet (IDs only)
cloudron list --tag web # filter by tag
cloudron status --app <app> # app details (status, domain, memory, image)
cloudron inspect # raw JSON of the Cloudron server
```
### App lifecycle
```bash
cloudron install # install app (on-server build or --image)
cloudron update --app <app> # update app (rebuilds or uses --image)
cloudron uninstall --app <app>
cloudron repair --app <app> # reconfigure app without changing image
cloudron clone --app <app> --location new-location
```
`cloudron install` and `cloudron update` accept:
- `--image <repo:tag>` — use a pre-built Docker image
- `--no-backup` — skip backup before update
- `-l, --location <subdomain>` — set the app location
- `-s, --secondary-domains <domains>` — secondary domain bindings
- `-p, --port-bindings <bindings>` — TCP/UDP port bindings
- `-m, --memory-limit <bytes>` — override memory limit
- `--versions-url <url>` — install a community app from a CloudronVersions.json URL
### Run state
```bash
cloudron start --app <app>
cloudron stop --app <app>
cloudron restart --app <app>
cloudron cancel --app <app> # cancel pending task
```
### Logs
```bash
cloudron logs --app <app> # recent logs
cloudron logs --app <app> -f # follow (tail)
cloudron logs --app <app> -l 200 # last 200 lines
cloudron logs --system # platform system logs
cloudron logs --system mail # specific system service
```
### Shell and exec
```bash
cloudron exec --app <app> # interactive shell
cloudron exec --app <app> -- ls -la /app/data # run a command
cloudron exec --app <app> -- bash -c 'echo $CLOUDRON_MYSQL_URL' # with env vars
```
### Debug mode
When an app keeps crashing, `cloudron exec` may disconnect. Debug mode pauses the app (skips CMD) and makes the filesystem read-write:
```bash
cloudron debug --app <app> # enter debug mode
cloudron debug --app <app> --disable # exit debug mode
```
### File transfer
```bash
cloudron push --app <app> local.txt /tmp/remote.txt # push file
cloudron push --app <app> localdir /tmp/ # push directory
cloudron pull --app <app> /app/data/file.txt . # pull file
cloudron pull --app <app> /app/data/ ./backup/ # pull directory
cloudron sync push --app <app> ./local/ /app/data # sync local contents -> remote (changed files only)
cloudron sync push --app <app> ./local /app/data # sync local dir itself into /app/data/local
cloudron sync push --app <app> file.txt /app/data # sync single file -> remote
cloudron sync pull --app <app> /app/data/ ./local # sync remote contents -> local (changed files only)
cloudron sync pull --app <app> /app/data ./local # sync remote dir itself into ./local/data
cloudron sync push --app <app> ./local/ /app/data --delete # also delete remote-only files
cloudron sync pull --app <app> /app/data/ ./local --delete # also delete local-only files
```
A trailing slash on the source syncs its contents; without it, the directory itself is placed inside the destination (rsync convention).
Use `--delete` to remove files present only on the destination side. Use `--force` to remove files blocking directory creation.
For directory transfers, prefer `cloudron sync`; keep `cloudron push`/`pull` for one-off file copy and stream-oriented use cases.
### Environment variables
```bash
cloudron env list --app <app>
cloudron env get --app <app> MY_VAR
cloudron env set --app <app> MY_VAR=value OTHER=val2 # restarts app
cloudron env unset --app <app> MY_VAR # restarts app
```
### Configuration
```bash
cloudron set-location --app <app> -l new-subdomain
cloudron set-location --app <app> -s "api.example.com" # secondary domain
cloudron set-location --app <app> -p "SSH_PORT=2222" # port binding
```
### Backups
```bash
cloudron backup create --app <app> # create backup
cloudron backup list --app <app> # list backups
cloudron restore --app <app> --backup <backup-id> # restore from backup
cloudron export --app <app> # export to backup storage
cloudron import --app <app> --backup-path /path # import external backup
```
Backup encryption utilities (local, offline):
```bash
cloudron backup decrypt <infile> <outfile> --password <pw>
cloudron backup decrypt-dir <indir> <outdir> --password <pw>
cloudron backup encrypt <infile> <outfile> --password <pw>
```
### Utilities
```bash
cloudron open --app <app> # open app in browser
cloudron init # create CloudronManifest.json + Dockerfile
cloudron completion # shell completion
```
## CI/CD integration
Use `--server` and `--token` to run commands non-interactively. Get API tokens from `https://my.example.com/#/profile`:
```bash
cloudron update \
--server my.example.com \
--token 001e7174c4cbad2272 \
--app blog.example.com \
--image username/image:tag
```
## Global options
These apply to most commands:
| Option | Purpose |
|--------|---------|
| `--server <domain>` | Target Cloudron server |
| `--token <token>` | API token (for CI/CD) |
| `--allow-selfsigned` | Accept self-signed TLS certificates |
| `--no-wait` | Do not wait for the operation to complete |
## Common workflows
### Check and restart a misbehaving app
```bash
cloudron status --app <app>
cloudron logs --app <app> -l 100
cloudron restart --app <app>
```
### Debug a crashing app
```bash
cloudron debug --app <app>
cloudron exec --app <app>
# inspect filesystem, check logs, test manually
cloudron debug --app <app> --disable
```
### Backup and restore
```bash
cloudron backup create --app <app>
cloudron backup list --app <app>
# note the backup ID
cloudron restore --app <app> --backup <id>
```
### Set env vars for an app
```bash
cloudron env set --app <app> FEATURE_FLAG=true DEBUG=1
# app restarts automatically
cloudron logs --app <app> -f
```
---
> Source: [benneic/cloudron-activepieces](https://github.com/benneic/cloudron-activepieces) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
设置
应用定位
应用程序生命周期
调试模式
文件传输
文件/命令 -> cloudron · ~/.cloudron.json · cloudron login my.example.com --allow-selfsigned · --app · CloudronManifest.json · appId · cloudron install · cloudron update
内容校验值 -> f4e21f5fdca4
当前原文的自动摘译,尚未人工审校。
设置
令牌存储在
~/.cloudron.json中。对于自签名证书:cloudron login my.example.com --allow-selfsigned应用定位
大多数命令需要
--app来指定哪个应用程序:当从具有CloudronManifest.json的目录和之前安装的应用程序运行时,CLI 会自动检测该应用程序(在每个目录配置中存储为appId)。应用程序生命周期
cloudron install和cloudron update接受:--image <repo:tag>— 使用预构建的 Docker 镜像--no-backup— 更新前跳过备份-l, --location <subdomain>— 设置应用程序位置-s, --secondary-domains <domains>— 辅助域绑定调试模式
当应用程序持续崩溃时,
cloudron exec可能会断开连接。调试模式暂停应用程序(跳过 CMD)并使文件系统读写:文件传输
源上的尾部斜杠同步其内容;如果没有它,目录本身将被放置在目标内部(rsync 约定)。使用
--delete删除仅存在于目标端的文件。使用--force删除阻止目录创建的文件。对于目录传输,首选cloudron sync;保留cloudron push/pull用于一次性文件复制和面向流的用例。