CLI reference

pikku cloud login, link, deploy plan/apply, logs, metrics.

The CLI is optional. Everything it does — deploying, viewing logs, checking metrics — is also available in the browser console, so you never have to touch a terminal. The CLI exists for people who prefer working in the terminal or want to script Pikku Studio Cloud into CI. If that's not you, skip this page.

Terminal screenshot showing the core commands in sequence — pikku cloud login, link, deploy plan, deploy apply — with the deploy plan output (a plain-English summary of pending changes) highlighted, callout: "Plan shows what will change; apply makes it happen."

The commands

CommandWhat it does
pikku cloud loginAuthenticates the CLI with your Pikku Studio Cloud account.
pikku cloud linkConnects a local project to Pikku Studio Cloud so the CLI knows what it's deploying.
pikku cloud deploy planPreviews what a deploy would change — and changes nothing.
pikku cloud deploy applyActually performs the deploy.
pikku cloud logsStreams your app's logs to the terminal.
pikku cloud metricsShows your app's metrics from the terminal.

plan vs. apply

The distinction worth internalizing:

  • deploy plan is read-only. It shows you a summary of exactly what would change if you deployed. It touches nothing — run it as often as you like to sanity-check before shipping.
  • deploy apply is the action. It performs the deploy described by the plan.

This mirrors the same preview-then-confirm flow you get in the console. See Deployments for the concept behind it.

Typical sequence

# Authenticate once
pikku cloud login

# Connect this project to Pikku Studio Cloud
pikku cloud link

# Preview what will change (changes nothing)
pikku cloud deploy plan

# Ship it
pikku cloud deploy apply

The takeaway

Every console action has a CLI equivalent for scripting and CI — but you don't have to use it. Reach for the CLI only if you prefer the terminal.

Where to go next