← Back to context Comment by threecheese 4 days ago Do you have an example? Sounds interesting. 8 comments threecheese Reply PufPufPuf 4 days ago Here's my modest collection of global tools I install in my dotfiles: https://github.com/JanPokorny/dotfiles/blob/master/dot_confi...Projects then have their own dependencies, e.g. https://github.com/i-am-bee/agentstack/blob/main/mise.tomlMise also has a task runner which automatically uses correct tools. Onboarding a new team member is super easy now, they just need Mise, "mise install" and they're up. jrop 3 days ago I really prefer to lock the version numbers instead: mise use -g somepackage --pin I can commit/rollback to known good versions. To upgrade: mise up -il Not so long ago, I was outspoken against mise. I've since come around. It truly is a fantastic tool. PufPufPuf 3 days ago Mise now has lockfiles as a stable feature, which has the benefit of hash checking if you use Mise in a CI environment! stouset 3 days ago What were your criticisms, and what changed? mmcclure 3 days ago I've been using mise as a pure version manager for a pretty long time, and I had no idea you could use it for general tools like this. snthpy 3 days ago Same srcrip 3 days ago How does this even work? How does mise know how to install these things? c-hendricks 3 days ago Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/
PufPufPuf 4 days ago Here's my modest collection of global tools I install in my dotfiles: https://github.com/JanPokorny/dotfiles/blob/master/dot_confi...Projects then have their own dependencies, e.g. https://github.com/i-am-bee/agentstack/blob/main/mise.tomlMise also has a task runner which automatically uses correct tools. Onboarding a new team member is super easy now, they just need Mise, "mise install" and they're up. jrop 3 days ago I really prefer to lock the version numbers instead: mise use -g somepackage --pin I can commit/rollback to known good versions. To upgrade: mise up -il Not so long ago, I was outspoken against mise. I've since come around. It truly is a fantastic tool. PufPufPuf 3 days ago Mise now has lockfiles as a stable feature, which has the benefit of hash checking if you use Mise in a CI environment! stouset 3 days ago What were your criticisms, and what changed? mmcclure 3 days ago I've been using mise as a pure version manager for a pretty long time, and I had no idea you could use it for general tools like this. snthpy 3 days ago Same srcrip 3 days ago How does this even work? How does mise know how to install these things? c-hendricks 3 days ago Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/
jrop 3 days ago I really prefer to lock the version numbers instead: mise use -g somepackage --pin I can commit/rollback to known good versions. To upgrade: mise up -il Not so long ago, I was outspoken against mise. I've since come around. It truly is a fantastic tool. PufPufPuf 3 days ago Mise now has lockfiles as a stable feature, which has the benefit of hash checking if you use Mise in a CI environment! stouset 3 days ago What were your criticisms, and what changed?
PufPufPuf 3 days ago Mise now has lockfiles as a stable feature, which has the benefit of hash checking if you use Mise in a CI environment!
mmcclure 3 days ago I've been using mise as a pure version manager for a pretty long time, and I had no idea you could use it for general tools like this. snthpy 3 days ago Same
srcrip 3 days ago How does this even work? How does mise know how to install these things? c-hendricks 3 days ago Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/
c-hendricks 3 days ago Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/
Here's my modest collection of global tools I install in my dotfiles: https://github.com/JanPokorny/dotfiles/blob/master/dot_confi...
Projects then have their own dependencies, e.g. https://github.com/i-am-bee/agentstack/blob/main/mise.toml
Mise also has a task runner which automatically uses correct tools. Onboarding a new team member is super easy now, they just need Mise, "mise install" and they're up.
I really prefer to lock the version numbers instead:
I can commit/rollback to known good versions. To upgrade:
Not so long ago, I was outspoken against mise. I've since come around. It truly is a fantastic tool.
Mise now has lockfiles as a stable feature, which has the benefit of hash checking if you use Mise in a CI environment!
What were your criticisms, and what changed?
I've been using mise as a pure version manager for a pretty long time, and I had no idea you could use it for general tools like this.
Same
How does this even work? How does mise know how to install these things?
Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.
It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/