Remote Devenv via Devenv From

After my last post Domen graciously reached out to talk about my use case and to gather my feedback and he very quickly spun out a branch that became out-of-tree devenvs. I have been using devenv --from daily for months, and it works famously. I can store a configuration for running outside a client's repo their repo and track it in git. This allows me to be reliable and reproducible across client commitments, without polluting their source control with Evan-specific config files. (Not everyone wants the gilded cage of Nix!) This week I realized I'd been using it without a hitch for several new projects, so it was time to say "it's ready!"1 Presently, I keep a single devenv config repo per client, setting up separate projects as profiles2. Secrets get loaded via something secure, not loaded into my git repo. If I need a new profile, LLM coding agents do a good job scanning code manifests and the README.md to figure out what is needed for a new profile. I then just have to <c-r> this…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town