Starting spinuptui from inside a site's checkout, where many of us live all day, could quietly feed that site's own .env into what the app does. This patch closes that off.
Fixed
pull dbworks when launched from inside a site's checkout. Bun auto-loads the.envof the directory you start it in, and every process spinuptui spawned inherited it. So a Bedrock site's ownDB_*values reachedwpas real environment variables. Some Bedrock configs then read blank database credentials, and the pre-import backup failed withAccess denied for user '<you>'@'localhost' (using password: NO). Keys from the launch directory's.envare now dropped at startup, and every child process gets the cleaned environment. Anything you exported in your shell is kept.- A site's
.envcan no longer supply your DNS provider credentials. The names are generic, and Bedrock sites commonly keep S3 media keys underAWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY. Launched from such a checkout, spinuptui used them as its Route 53 credentials, silently overriding the ones in config. Provider keys (AWS_*,CLOUDFLARE_API_TOKEN,GODADDY_API_*) from a.envare now honored only in spinuptui's own project directory. Shell-exported keys work from anywhere, as before. pull db's "Access denied" hint points Bedrock and Radicle sites at their.env. It used to blamewp-config.phpfor every site, but those stacks keep their database credentials in.env.
Notes
- If you were syncing from inside one site's checkout on 0.26.0, it's worth a quick check that the right local database got the import. Depending on a site's Bedrock config, the leaked values could fail outright or, in principle, point
wpat the launch site's database instead.