Individual skill

openship-deploy

This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.

plugins/openship-skills/skills/openship-deploy/SKILL.md

Read pinned source

Source commit 4f2b4bc9a74024397b4688cbafd1ae538a83a5fb

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,200
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
github Repository topic
commit-message Repository topic
pull-requests Repository topic
cursor Repository topic
gemini-cli Repository topic
codex Repository topic
codex-cli Repository topic
plugin Repository topic
ai-agents Repository topic
devops Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

LICENSEasset · 11,358 bytes
SKILL.mdcore · 4,068 bytes
SKILL.mdcore · 4,068 bytes
SKILL.mdcore · 4,068 bytes
references/cli/access.mdxasset · 7,811 bytes
references/cli/automation.mdxasset · 3,438 bytes
references/cli/deploy.mdxasset · 4,544 bytes
references/cli/edge.mdxasset · 2,050 bytes
references/cli/index.mdxasset · 3,293 bytes
references/cli/projects.mdxasset · 5,231 bytes
references/cli/run.mdxasset · 2,654 bytes
references/cli/self-host.mdxasset · 4,852 bytes
references/guides/backups-restore.mdxasset · 13,188 bytes
references/guides/custom-domains.mdxasset · 22,873 bytes
references/guides/logs-monitoring.mdxasset · 12,066 bytes
references/guides/migrate-control-plane.mdxasset · 10,692 bytes
references/guides/persistent-storage.mdxasset · 7,174 bytes
references/guides/rollback-redeploy.mdxasset · 16,686 bytes
references/guides/self-hosted-github-app.mdxasset · 6,757 bytes
references/guides/updating.mdxasset · 8,280 bytes
references/troubleshooting/deployments.mdxasset · 18,482 bytes
references/troubleshooting/domains-ssl.mdxasset · 16,759 bytes
references/upstream.jsonasset · 7,755 bytes

Read excerpt


# Deploy and operate OpenShip

Prefer the CLI and an existing self-hosted instance. Use a cloud or desktop workflow when the user requests it. Keep application deployments separate from installing or upgrading the OpenShip control plane.

## Choose the instance and command

- Check `openship --version` and `openship context list`. Select the intended self-hosted context before a remote operation. Never assume the active context points to the user's server.
- Use native commands with the global `--json` flag. Read [CLI access](references/cli/access.mdx) for context and authentication details, and [automation](references/cli/automation.mdx) for CI logins and scripts that pass explicit project IDs. Do not print stored tokens.
- Check the installed command's `--help`. Use `openship api` for routes without a working command, after checking the matching implementation. In v0.8.0, `server ssh` is a stub despite appearing in help. A successful help command does not prove an operation works.
- [upstream.json](references/upstream.json) records the bundled release, exact source URLs, and hashes. If the installed CLI or server differs, verify the relevant source at that version before relying on a flag or API contract.

## Deploy an application

1. Inspect the repository, existing project link, build entry point, service topology, persistent volumes, and current domain ownership. Use [projects and services](references/cli/projects.mdx) for commands.