Ghostable now works with Lerd. Run PHP and Artisan commands with your Ghostable environment values, without exporting a plaintext .env file. Values are decrypted locally and passed to the command you run. ghostable.dev/blog/ghostable…

Ghostable V3 is a free, account-free Git-backed environment workflow with an optional visual desktop app for people who prefer to work outside the terminal. ghostable.dev/blog/introduci…

A server-less CLI for local-first environment management: projects, environments, variables, devices, schema validation, agent guidance, and signed-style activity records. ghostable.dev/blog/ghostable…

The thing in the screenshot 😄 Ghostable is desktop-first .env management for dev teams. Safer sharing, validation, history, and less Slack-copy-paste chaos. You building something too?

Tools like goenv are solid for reading and working with .env files locally. Ghostable includes a CLI for that same kind of programmatic and command line usage: ghostable.dev/docs/cli Where things break down isn’t local access, it’s team coordination: keeping values consistent across local, staging, and production knowing what’s required vs optional tracking who changed what and when sharing access without passing raw secrets around Ghostable handles the workflow around environments, not just loading them.

.gitignore is table stakes, but it only solves “don’t commit the file.” It doesn’t solve sharing envs between devs, validating required keys, tracking changes, avoiding drift across staging/prod/local, or safely onboarding someone without pasting secrets into Slack. Ghostable is for the workflow around envs, not just hiding them from Git.

Short answer: Nope. ghostable.dev/blog/are-env-f…

That is the line that changes vendor risk. It changes compliance scope. It changes what your team has to prove, monitor, and trust. ghostable.dev/blog/differenc…

Don’t disagree, but also consider its current rate of improvement.

Mostly stuff that helps agents stop guessing. For me that means stack/context, architecture patterns, naming conventions, preferred libraries, testing expectations, commands they can run, things not to touch, and project-specific workflows. Basically “here’s how this app thinks.”

More like a master AGENTS.md file(s)

Docker might secrets help at runtime, but they don’t really solve how teams manage .env files across local/dev/staging. That’s usually where things fall apart. Sharing, syncing, and knowing what changed.

A practical setup flow for OpenClaw environment variables, including local files, host startup, Docker, and secret ownership. ghostable.dev/blog/openclaw-…

You can’t fake trust in a secrets product. Ghostable is still early, and I’d rather be honest about that than pretend otherwise. I’m looking for a small number of Laravel teams to use it for free, give blunt feedback, and help shape a product that actually earns trust. If that sounds like your team, sign up at ghostable.dev or reply/DM me.

Consider Ghostable’s free tier for secrets management (even for vibe work)…security is getting harder not easier ghostable.dev

Real question: Are you actually confident in your .env setup right now? Or just assuming it’s fine?

The most secure environment secrets manager. ghostable.dev

The most secure environment secrets manager on the market. Facts.

toddshelton.com/t-shirts Lots of size options and also do made to order if you want it totally custom.