$ poco app
cloud pod operations against GKE deployments (kubectl wrappers with the Polypoint app registry baked in)
- logs
- exec
- port-forward
- port-forward-debug
- restart
- status
- ping
- health
- scale
The polypoint cloud companion. GKE pods, local stacks, builds, databases and vaults — one CLI, one TUI, every environment.
$ curl -fsSL https://get-poco.polypoint.dev | bash
Needs an authenticated gcloud with your polypoint Google account — that's the whole gate. Once installed, poco keeps itself current silently on the stable channel; early builds via poco update channel preview.
The installer always ships stable (v0.2.3). Opt in to early builds from inside poco — poco update channel preview — and back out anytime with poco update channel stable.
cloud pod operations against GKE deployments (kubectl wrappers with the Polypoint app registry baked in)
build cloud monorepo projects + docker images (mvnw + jib; renamed v1 build-zinc)
discovery: list and search every registered poco command
print a shell completion script (bash, zsh, fish) to stdout — or `install` it
inspect and edit `~/.poco/config.<profile>.yaml`
surgical edits to the on-prem config-generator data in portal-core Postgres (templates, available keys, tenant configs)
port-forward an app's Postgres/MySQL (or the shared Redis) to localhost
the inner loop: build → deploy → follow logs (cloud with -N, compose with --local); --watch redeploys on change
check local prerequisites for the Compose dev flow (--fix also repairs what it can)
deploy your local image build to a GKE namespace under a custom tag, and withdraw it again (M9)
drive the docker-compose local-dev stack (wraps the cloud/docker Makefile)
serve poco as an MCP stdio server for agents (read-only tools; see `mcp tools`)
on-prem (Nomad) operations: deploy/withdraw custom jars, restart, status, logs, port-forward
cluster-level operations (cleanup and maintenance against a whole GKE cluster)
locate your cloud monorepo and save it to the active profile (first-run wizard)
manage `$name` snippets in the active profile config
where am I pointed, what custom deploys are live, what runs locally, what jobs are open
check for a newer poco release and install it (see also: update channel | rollback)
HashiCorp Vault operations against the active GKE cluster (uses kubectl exec; no driver)