Then it struck me. I already define project dependencies with mise. What if we could build a container on the fly for any project by reading the mise config?
I've been using agent-en-place for a couple of weeks now, and it's working great! I'd love to hear what y'all think
This allows you to not only run current commands in a containerized environment, but also any point in history
> .go-version
I would not call this idiomatic Go, you can get the version my project requires from my go.mod file. Imo, a single file with the inputs your tool needs would be preferable to a bunch of files with a single line, but ideally it can infer that on it's own by looking at the language files that already exist
sshine•2w ago
verdverm•2w ago
sshine•2w ago
Most of those dime-a-dozen solutions employ Docker, so if you like to work inside a container, that's great.
verdverm•2w ago
I use Dagger, which is BuildKit based underneath, and aligns closely with Dockerfiles, but is far more flexible and is accessible from many programming languages
so in this sense "it's not my own take", but both of these are our own "take" on assembling several pieces of technology to realize a certain application feature. It's the feature that is the "dime-a-dozen" and most people largely don't care what technologies you choose to deliver that feature
mistrial9•2w ago