Existing Projects

Start on a dedicated branch with a known-good local .env. Confirm the application boots before migration, verify plaintext env files are ignored, and keep a secure copy outside the repository until the new baseline has been tested.

$ git switch -c adopt-ghostable-v3
$ git check-ignore .env
 

$ ghostable setup --seed-dotenv --create-example --agent-instructions
$ ghostable env diff --env default --file .env
$ ghostable validate --env default
 

Setup encrypts the imported values locally and records the reason as a setup seed. The generated .env.example defaults to retaining non-sensitive example values while blanking values that look sensitive.

The adopt command produces a plain-text prompt that a developer or coding agent can use to assess schema rules, annotations, example-file drift, hygiene, and optional CI work:

$ ghostable adopt --all --ci
 

Treat the prompt as a review aid. It is designed to separate evidence-backed changes from open questions such as secret ownership, deployment scope, and rotation expectations.

1. Compare encrypted state to the working file with env diff.
2. Add validation rules for values whose format or presence is understood.
3. Generate .env.example and review every retained example value.
4. Run ghostable review to find changed-code ENV drift and hard-coded secrets.
5. Run the application using ghostable env run or a freshly pulled file.

$ ghostable example generate --dry-run
$ ghostable review
$ ghostable env run --env default -- php artisan test