Skip to main content
Ghostable CLI 1.x is legacy. Prefer the current Desktop docs or CLI 2.x docs for new work.

deploy:forge

Deploy Ghostable-managed variables during a Laravel Forge deployment script.
Merges managed keys into Forge’s environment and (optionally) produces an encrypted env bundle.

Options

--encrypted
flag
Bundle non-secret variables into an encrypted file for runtime decryption. Ghostable will provision the required LARAVEL_ENV_ENCRYPTION_KEY in Forge.
--plan
flag
Print the variable names that would be deployed without changing anything.

Example

Deployment Script

deploy:vapor

Deploy Ghostable-managed variables during a Laravel Vapor build.
Can optionally ship an encrypted env file compatible with Vapor runtime decryption.

Options

--vapor-env
string
required
Target Vapor environment (e.g., production, staging). Determines which Ghostable environment to pull.
--encrypted
flag
Bundle non-secret variables into an encrypted file for runtime decryption. Ghostable injects LARAVEL_ENV_ENCRYPTION_KEY into the Vapor environment.
--plan
flag
Print the variable names that would be deployed without changing anything.

Example

vapor.yml

deploy:cloud

Deploy Ghostable-managed variables to Laravel Cloud during your pipeline step.
Behavior mirrors deploy:forge (merge) with optional encrypted bundle support.

Options

--encrypted
flag
Bundle non-secret variables into an encrypted file for runtime decryption. Ghostable sets the matching decryption key in Cloud.
--plan
flag
Print the variable names that would be deployed without changing anything.

Example

Deploy Script

env:deploy

A generic deployment command for non-laravel specific deployments. OpenClaw uses this generic env-file workflow instead of a provider-specific deploy command. See the OpenClaw integration guide for the Docker Compose and host-runtime pattern.

Options

--validate
flag
default:"true"
Require the environment pass validation.

Shared requirements

  • GHOSTABLE_CI_TOKEN must be available in the environment where the command runs (CI secrets, Forge/Cloud env, or local shell for manual runs).
Use --plan in CI to print the intended changes before applying them.