Cloud CLIs
The command-line tools for AWS, Google Cloud, Oracle Cloud, Hetzner, Cloudflare Tunnel, Fly.io, Railway, Render, Koyeb, Neon and Supabase.
One command-line tool per cloud or hosting service the workstation deploys to. Each logs in once through the browser and keeps its token under the home folder.
On the workstation
-
Installed by the
awscli,oci-cli,hcloud,cloudflared,flyctl,railway,render,koyeb,neonctlandsupabaseformulae and thegcloud-clicask. -
Tokens stay out of the dotfiles: chezmoi manages none of the folders where these tools keep their logins, such as
~/.awsand~/.config/gcloud. -
supabase startruns its local stack in Docker, so Colima must be running.
Keys and commands
| Key or command | Does |
|---|---|
|
Log in to AWS through single sign-on |
|
Show which AWS account and role are active |
|
Log in to Google Cloud |
|
List the Google Cloud accounts and projects set up |
|
Add a Hetzner project with its API token |
|
List the Hetzner servers |
|
Share a local service on a temporary public URL |
|
Build and deploy the app in this folder to Fly.io |
|
Follow a Fly.io app’s logs |
|
Deploy this folder to Railway |
|
Branch a Neon database, data included |
|
Print the connection string of a branch |
|
Run Supabase locally |
|
Start a new SQL migration |
|
Apply the migrations to the linked project |
With zc-workstation
The cloud CLIs sit under a # Cloud section of the Brewfile. A new one goes
in the same section with its reason, and one you stop using leaves with its
package:
$ zc-workstation add -target packages -section Cloud -why "DigitalOcean from the command line" brew:doctl
$ zc-workstation remove -target packages brew:railway
Edit this page Last updated