deploy
/deploy
Add or redeploy application stacks on a VPS that ALREADY runs bento, via SSH. Drives bento's unattended Step 3 (BENTO_APPS) for the chosen apps, reconciles state against Portainer, verifies each app, and reports URLs + bootstrap artifacts. Use when the user says "add n8n to my server", "deploy chatwoot on my bento box", "install another app". For a brand-new server use the install skill instead.
- Author
- felipefontoura ↗
- Repository
- bento ↗
- Licence
- MIT
- Last repository change
- 05.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 05.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Add or redeploy application stacks on a VPS that ALREADY runs bento, via SSH. Drives bento's unattended Step 3 (BENTO_APPS) for the chosen apps, reconciles state against Portainer, verifies each app, and reports URLs + bootstrap artifacts. Use when the user says "add n8n to my server", "deploy chatwoot on my bento box", "install another app". For a brand-new server use the install skill instead.
Triggers from the description
Original author description
Add or redeploy application stacks on a VPS that ALREADY runs bento, via SSH. Drives bento's unattended Step 3 (BENTO_APPS) for the chosen apps, reconciles state against Portainer, verifies each app, and reports URLs + bootstrap artifacts. Use when the user says "add n8n to my server", "deploy chatwoot on my bento box", "install another app". For a brand-new server use the install skill instead.
How it works
SKILL.md has no level-two headings · 82 lines, 559 words
SKILL.md preview
---
name: deploy
description: Add or redeploy application stacks on a VPS that ALREADY runs bento, via SSH. Drives bento's unattended Step 3 (BENTO_APPS) for the chosen apps, reconciles state against Portainer, verifies each app, and reports URLs + bootstrap artifacts. Use when the user says "add n8n to my server", "deploy chatwoot on my bento box", "install another app". For a brand-new server use the install skill instead.
---
You are operating bento on a remote machine the user trusts you with. Narrate
before every state-changing step and stop on anything that smells off. Every
artifact and message you produce stays in English.
# When to invoke
The user has a server that ALREADY has bento installed and wants more apps:
- "add n8n and typebot to my VPS"
- "deploy chatwoot on `<host>`"
- "install paperclip on my bento server"
If bento is NOT yet installed on the host, this is the wrong skill — use
`/bento:install` (fresh-VPS bootstrap). If the user wants logs/restart/scale of
an already-running app, point them at Portainer (`https://portainer.<domain>`).
# Inputs to gather
| Input | Source | Validation |
|---|---|---|
| VPS host | user message; ask if missing | reachable via SSH |
| SSH user | default `root`; ask if otherwise | has sudo or is root |
| apps to deploy | user message (CSV) | each must be a directory under `stacks/app/` on the host clone |
| per-app overrides | only if the user wants a non-default hostname/secret | passed as `BENTO_ENV_<STACK>_<VAR>` |
Use `AskUserQuestion` for anything missing. Don't guess an app name.
# Pre-flight (mandatory)
1. SSH reachable: `ssh -o ConnectTimeout=5 "$user@$host" "echo SSH_OK"`.
2. Confirm bento is installed: `ssh "$user@$host" "test -f ~/.config/bento/state.json && echo BENTO_OK"`. If absent, stop — tell the user to run `/bento:install` first.
3. List deployable apps so you validate the requested set against reality:
```bash
ssh "$user@$host" "ls /root/.local/share/bento/stacks/app"
```
Reject any requested app not in that list and show the valid options.
4. DNS for any NEW public hostname: `dig +short A "<app>.<base_domain>" @1.1.1.1`. The wildcard `*.<base_domain>` from the original install normally already covers it; warn only if it doesn't resolve to the VPS IP.
# Deploy — unattended only
Never drive bento's interactive TUI over SSH (gum prompts hang without a real
terminal). Re-run bento's installer in unattended mode with `BENTO_APPS` set to
ONLY the new apps. bento reconciles `state.stacks` against Portainer on entry to
`unattended_step3`, so orphaned state from a Portainer-side deletion won't
short-circuit the deploy.
```bash
ssh "$user@$host" "\
BENTO_UNATTENDED=1 \
BENTO_APPS=<comma,separated,apps> \
${BENTO_ENV_OVERRIDES:+$BENTO_ENV_OVERRIDES} \
bash /root/.local/share/bento/install.sh"
```
Per-app override example (non-default hostname):
`BENTO_ENV_N8N_N8N_HOST=automation.example.com`.
Stream stdout. Watch for the failure patterns in the `install` skill's
"Failure-mode library" (409 stack-already-exists, ENOTFOUND postgres, directory
nonexistent, post-deploy ran too early) — the recoveries there apply verbatim.
Identify the pattern before running any recovery.
# Verify before reporting (per app)
1. **Swarm**: `docker service ls --filter name=<stack>_ --format '{{.Name}} {{.Replicas}}'` shows the expected replicas (n8n has 3 services).
2. **HTTPS**: `curl -sI --max-time 15 https://<app>.<base_domain>/` returns a sane status (2xx/3xx or the app's expected code).
3. **DB** (if the stack uses shared postgres): `psql -lt | grep -w <stack>` finds the DB on the postgres container.
4. **Stack-specific artifact**: read `stacks/app/<stack>/install.sh` to know what it bootstrapped (e.g. paperclip's `~/.config/bento/paperclip-invite-url.txt`).
Don't trust an install.sh "is ready" line — verify against Swarm + HTTPS + the
marker file, always.
# Report back
- Per-app URL (from `state_get .bootstrap.base_domain` + each manifest's `post_deploy_url`).
- Any bootstrap invite URLs (paperclip marker file is the canonical one).
- If any deployed app is an AI runtime (paperclip, openclaw, cli-proxy-api) and
no provider key is registered yet, point at `/bento:auth`.
- Warnings (DNS still propagating, memory tight).
Format URLs as clickable links and quote credentials verbatim.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · felipefontoura/bento | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| microsoft/power-platform-skills | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| wraith-proxy/wraith-skills | 100 | MIT |
| jikig-ai/soleur | 100 | Apache-2.0 |
| curiositech/windags-skills | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 7fa06049878f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100update
Update an existing bento install to the latest code and redeploy its managed stacks, via SSH. Re-runs the bento bootstrap unattended (re-clones the chosen ref, re-applies idempotently, redeploys BENTO_MANAGED stacks). Use when the user says "update bento", "pull the latest… - 100install
Drive an end-to-end bento install on a FRESH Ubuntu/Debian VPS via SSH — pre-flight checks, unattended one-liner, post-hardening reboot, infra + app deploys, recovery from the failure modes that historically required manual operator intervention, and a final report with URLs +… - 90install-open-mail-server
Installs Open Mail Server on a Linux VPS over SSH. Asks for the server host, username, and password, installs Docker when it is missing, copies this project and its Compose file, and starts the container. Use when the user asks to install, deploy, or set up Open Mail Server on a… - 100vps-panel-3xui
在一台 Linux VPS 上全自动部署、重装或迁移 3x-ui(x-ui)代理面板——SSH 探测、非交互安装、验收、备份数据库、凭据落盘一次做完。当用户提供 VPS 的 IP / SSH 端口 / root 密码,并说"搭面板""装 3x-ui""节点面板""重装面板""续费后恢复面板""帮我配代理服务器"时使用;也用于排查面板打不开、密码登不上、端口不通、HTTP/HTTPS 协议混淆等问题。 - 90vps-deploy
Deploy an owned application to an explicitly authorized VPS with versioned artifacts, service identity and live health evidence. Use when publishing or repairing a known server deployment; preserve existing services and separate local preparation from remote execution. - 100vps-deploy-golden-path
Deploy a Node app to a VPS with build ordering, health checks, and a sentinel wired in. Use when setting up deployment for a VPS-hosted app, when a deploy shipped stale code or wedged on a git conflict, when a deploy reports success but the app is down, or when auditing existing…