Replies: 2 comments
-
I think this sort of thing makes sense from a general standpoint. I'm not sure about using a directory like |
Beta Was this translation helpful? Give feedback.
-
Yes totally, something like just providing a single word should look into this local directory first, because I wouldn't wanna start remote and might prefer to version my templates with my dotfiles instead of each in a separate repository, for my local only templates but then providing with a slash might be considered a GitHub repo (maybe also configurable via sth like MISE_TEMPLATE_DEFAULT_REMOTE) or you provide an absolute URI which gets the repo |
Beta Was this translation helpful? Give feedback.
-
Would be fantastic to be able to pre-define config templates ie in
$MISE_DATA_DIR/config-templates
or whatever which you can then select viamise generate config --template [name-of-tpl]
or maybe just
mise generate config [name-of-tpl]
This way different environments/projects could have different templates like for node I could pre-define
which I luckily found in #3330
This might actually be interesting to add to the default, I think, but maybe not, in anyway this got me to this idea. 🤓
After the devtools episode I'm doubling down on mise, just moved all package.json scripts to .mise.toml and started using
jdx/mise-action
🥳Beta Was this translation helpful? Give feedback.
All reactions