Migrating from v1
Ghaymah CLI v2 replaced the verbose, UUID-driven gy resource commands with a simple,
name-driven workflow. Here’s how the old commands map to the new ones.
Command mapping
Section titled “Command mapping”| v1 command | v2 command |
|---|---|
gy auth login |
gy login |
gy auth signup |
gy signup |
gy auth status |
gy whoami |
gy auth logout |
gy logout |
gy resource app init --project-id <UUID> |
gy deploy |
gy resource app launch |
gy deploy |
gy resource app get |
gy list apps or gy info |
gy resource app get <UUID> |
gy info <name> |
gy resource app delete <UUID> |
gy delete app <name> |
gy resource project get |
gy list projects |
gy resource project delete <UUID> |
gy delete project <name> |
gy resource app logs <UUID> |
gy logs <name> |
What changed
Section titled “What changed”| Before | After |
|---|---|
gy resource app init --project-id <UUID> |
gy deploy |
| Write a Dockerfile by hand | Auto-generated for your stack |
| Memorize UUIDs | Friendly names everywhere |
| Figure out build steps | Auto-detected from your project |
| Parse raw JSON output | --json flag for AI/scripts |
| Read docs for an hour | gy deploy --wizard walks you through it |
What stayed the same
Section titled “What stayed the same”- The
gybinary name and install location (~/ghaymah/bin) - Account and credentials model
- Public URLs on
*.hosted.ghaymah.systems
Upgrade
Section titled “Upgrade”curl -sSL https://cliv2.ghaymah.systems/install.sh | bash -s -- --updateThen verify:
gy --versiongy whoami