2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill caprover-ci-deploys- _meta.json296 B
- SKILL.md5.5 KB
Overview
This skill deploys applications to CapRover and scaffolds GitHub Actions CI/CD workflows so you can trigger builds and releases by voice or command. It supports GitHub workflow_dispatch, CapRover webhook triggers, and direct CLI/app-token deploys. The skill also helps create workflow files, captain-definition, and required GitHub secrets for new projects.
How this skill works
The skill reads a local config.json that maps app names to CapRover and GitHub settings, then selects the best deployment strategy. If a GitHub workflow and token exist it triggers workflow_dispatch; if a CapRover webhook URL exists it posts to that webhook; otherwise it falls back to a CapRover app token or prompts for missing credentials. It reports API responses and can check recent GitHub Actions run status to confirm deployment results.
When to use it
- Deploy an app or trigger a specific branch build (e.g., "deploy myapp to main").
- Set up CI/CD for a new project with CapRover workflows and secrets.
- Add or update a GitHub Actions deploy workflow in a repository.
- Trigger a webhook-based rebuild from CapRover without logging into the dashboard.
- Check recent deploy status or list deployable apps from configuration.
Best practices
- Keep a single config.json (gitignored) with per-app settings: caprover URL, tokens, repo and workflow file names.
- Prefer GitHub workflow_dispatch when a repo workflow exists — it provides build visibility in Actions UI.
- Store CapRover host and app tokens in GitHub Actions secrets (CAPROVER_HOST, CAPROVER_APP_TOKEN).
- Use app tokens or webhooks instead of the master password for per-app deploys to limit scope.
- After triggering, verify the run via GitHub Actions API or Actions UI to confirm success.
Example use cases
- "Deploy myapp" triggers the preferred strategy for the default branch and returns the run ID or webhook response.
- "Deploy branch feat/ui to myapp" triggers workflow_dispatch with ref=feat/ui.
- Scaffold .github/workflows/deploy.yml and captain-definition for a new repo and instruct how to add required secrets.
- Trigger a CapRover webhook to rebuild an app configured to pull from the repo.
- Use caprover CLI with an app token to push an image or invoke a direct deploy when no workflow exists.
FAQ
A GitHub personal access token with repo and workflow scopes and the repo owner/name plus the workflow filename are required.
How does the skill choose which deploy strategy to use?
It checks config.json: if GitHub token + repo + workflow exist it uses workflow_dispatch, else it tries webhook URL, then app token, and finally prompts for missing info.
Can I deploy a specific branch or tag?
Yes — when triggering workflow_dispatch you can pass the git ref (branch or tag). Webhook triggers behave according to CapRover webhook configuration.