Live Vanta integration is live
Ghostable ✕ Laravel Forge

Ship environment changes with your Forge deploy script.

Let Ghostable refresh your Forge environment before config caching so every deploy carries the latest env vars—or an encrypted env file—without manual edits.

Why teams connect Ghostable with Laravel Forge
Forge-Native

Fits your deployment script

Place `npx ghostable deploy forge` before config:cache so every deploy pulls envs from Ghostable automatically.

No Drift

Ghostable is the source

Variables in Ghostable overwrite matching keys in Forge; anything unmanaged stays untouched.

Encrypted Option

Ship env files securely

Use `--encrypted` to generate .env.encrypted and keep secrets out of git while staying under size limits.

Set up in minutes

Turn on Laravel Forge syncing and forget about manual updates.

  1. 1

    Add your deployment token

    In Forge → Environment → Reveal, add GHOSTABLE_CI_TOKEN and GHOSTABLE_DEPLOY_SEED from Ghostable.

  2. 2

    Insert the deploy command

    In Site → Deployment Script, run `npx ghostable deploy forge` (optionally `--encrypted`) before config:cache.

  3. 3

    Deploy normally

    Trigger a deploy; Ghostable writes env vars into Forge and your script caches config with the updated values.

FAQs about Ghostable & Laravel Forge
Your Forge script runs `npx ghostable deploy forge`; Ghostable pushes your env vars into that site, logging each deploy for history.
Forge rollbacks only affect code—re-deploy from Ghostable if you need env changes. Removing a variable in Ghostable will not auto-delete it in Forge, so clean up unused values there.
Yes. Use `npx ghostable deploy forge --encrypted`; Ghostable generates LARAVEL_ENV_ENCRYPTION_KEY for you so Forge can decrypt at runtime.

More integrations

Explore other providers

Browse the growing lineup—new integrations land here as soon as we ship them.