🔧 Meet mise - a multi-purpose dev tool that handles:

• Tool installation (with version pinning!)
• Task running (like make/just)
• Environment variable management

Install specific versions effortlessly: mise use helm@3
Works seamlessly across macOS & Linux. Perfect for managing project-specific toolchains!

Read my post: https://blog.bitfoo.de/tools/mise/

#DevOps #linux #macos #engineering #tools #development #sysadmin #rust #cli #mise #DevTools #opensource #Softwaredevelopment #programming @jdx

Mise

Articles and stories about my life as a DevOps engineer.

Bitfoo's DevOps Site
@Bitfoo
And for some criticism
- will emit a four line warning every time when you run *any* command in a directory that has an untrusted config
- can't tell apart between the same tool with plugins installed for one project and configured without plugins in another project
@jdx
@mattesilver @jdx Thank you for your message. I do not understand what exactly you mean. Maybe you can an elaborate a bit more about your criticism.

@Bitfoo @jdx

Say you have two projects (a, b), both use tool x, but project b uses x with some plugins. Mise can't tell apart between x with plugins and without, it's installed in the same location.

The other thing is that mise requires you to register each config (add to trusted). If you clone a project that you only want to poke around, or use mise in a dev container, so that you don't add it to trusted, mise will complain at every command you run in that directory, bc mise takes over all invocations in the shell

@mattesilver @jdx now I understand.
The first critic is maybe more a feature request for @jdx and a more advanced usage of mise.
And the second one, yes I think this is a more or less of a problem tha mise outputs into the shell each time it encounters an error. But I am not sure how this could be prevented.

But I highly appreciate your feedback.