phala.toml is the project configuration file for Phala Cloud CLI. Place it in your project root to set default CVM identity, gateway settings, and API version for all CLI commands.
Quick Start
Create a minimal config with just a CVM name:CVM Identifier
Use thename field to identify your CVM. It’s human-readable and follows RFC 1123 hostname format.
If you have existing deployments using UUIDs or app IDs, those legacy fields still work. See Legacy Identifiers below.
Gateway Configuration
Configure custom gateway settings for CVM access:API Version
Rarely needed — the CLI defaults to the latest supported version:How the CLI Resolves CVM Identity
When you run commands likephala deploy or phala ssh, the CVM ID is resolved in this order:
- Interactive selection —
-ior--interactiveflag - Command-line flag —
--cvm-idor--uuid - phala.toml — configuration in the current directory
Legacy Identifier Fields
For backward compatibility, these fields are supported. Use them only for existing deployments.| Field | Format | Example |
|---|---|---|
id | Any string | "my-custom-id" |
uuid | UUID v4 | "550e8400-e29b-41d4-a716-446655440000" |
app_id | 40-char hex | "50b0e827cc6c53f4010b57e588a18c5ef9388cc1" |
instance_id | Instance ID | "instance_abc123xyz" |
id > uuid > app_id > instance_id > name. Specify only one to avoid confusion.
Migrating from UUID to Name
Schema Reference
Troubleshooting
CVM not found — Verify the name matches:phala cvms list. Check you’re in the right workspace.
File not found — Run phala init or ensure you’re in the correct directory.
Validation errors — Names must be 5–63 chars, lowercase, starting with a letter. UUIDs must be valid v4 format. Ports must be positive integers.
