docs: windows

Author: jdx

docs/faq.md

@@ -1,6 +1,8 @@
 # FAQs
 
-## I don't want to put a `.tool-versions` file into my project since git shows it as an untracked file
+## I don't want to put a
+
+`.tool-versions` file into my project since git shows it as an untracked file
 
 You can make git ignore these files in 3 different ways:
 
@@ -26,7 +28,8 @@ While this change is rolling out, there is some migration code that will move in
 the "nodejs" and "golang" directories to the new names. If this runs for you you'll see a message
 but it should not run again unless there is some kind of problem. In this case, it's probably
 easiest to just
-run `rm -rf ~/.local/share/mise/installs/{golang,nodejs} ~/.local/share/mise/plugins/{golang,nodejs}`.
+run
+`rm -rf ~/.local/share/mise/installs/{golang,nodejs} ~/.local/share/mise/plugins/{golang,nodejs}`.
 
 Once most users have migrated over this migration code will be removed.
 
@@ -134,9 +137,11 @@ setting `MISE_USE_VERSIONS_HOST=0`.
 
 ## Windows support?
 
-This is something we'd like to add! <https://github.com/jdx/mise/discussions/66>
+Very basic support for windows is currently available, however because Windows can't support asdf
+plugins, they must use core and vfox only—which means only a handful of tools are available on
+Windows.
 
-It's not a near-term goal and it would require plugin modifications, but it should be feasible.
+As of this writing, env var management and task execution are not yet supported on Windows.
 
 ## How do I use mise with http proxies?
 

docs/getting-started.md

@@ -187,7 +187,6 @@ Supported os/arch:
 - `linux-armv7-musl`
 
 If you need something else, compile it with `cargo install mise` (see below).
-[Windows isn't currently supported.](https://github.com/jdx/mise/discussions/66)
 
 ### apk
 
@@ -329,6 +328,14 @@ yum-config-manager --add-repo https://mise.jdx.dev/rpm/mise.repo
 yum install -y mise
 ```
 
+### Windows
+
+Download the latest release from [GitHub](https://github.com/jdx/mise/releases). Add the binary
+to your PATH and edit PATH to include the shims directory (by default:
+`%USERPROFILE%\.local\share\mise\shims`).
+
+Note that Windows support is very minimal for now.
+
 ## Shells
 
 ### Bash

docs/project-roadmap.md

@@ -1,14 +1,21 @@
 # Project Roadmap
 
-Issues marked ["enhancements"](https://github.com/jdx/mise/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement) are the best way to read about ideas for future
+Issues
+marked ["enhancements"](https://github.com/jdx/mise/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement)
+are the best way to read about ideas for future
 functionality. As far as general scope however, these are likely going to be focuses for 2024:
 
-* Tasks - this is the newest headline feature of mise and needs to be refined, tested, and iterated on before it can come out of experimental
+* Tasks - this is the newest headline feature of mise and needs to be refined, tested, and iterated
+  on before it can come out of experimental
 * Documentation website - we've outgrown what is mostly a single README
-* Supply chain hardening - securing mise is very important and this topic has had a lot of interest from the community. We plan to make several improvements on this front
-* Improved python development - better virtualenv integration, precompiled python binaries, and other areas are topics that frequently come up to improve
-* Improved plugin development - it's unclear what we'll do exactly but in general we want to make the experience of vending tools for asdf/mise to be better and safer.
-* GUI/TUI - While we're all big CLI fans, it still would be great to better visualize what tools are available, what your configuration is, and other things via some kind of UI.
+* Supply chain hardening - securing mise is very important and this topic has had a lot of interest
+  from the community. We plan to make several improvements on this front
+* Improved python development - better virtualenv integration, precompiled python binaries, and
+  other areas are topics that frequently come up to improve
+* Improved plugin development - it's unclear what we'll do exactly but in general we want to make
+  the experience of vending tools for asdf/mise to be better and safer.
+* GUI/TUI - While we're all big CLI fans, it still would be great to better visualize what tools are
+  available, what your configuration is, and other things via some kind of UI.
 
 ## Versioning
 
@@ -27,7 +34,14 @@ Each release will be small and incremental.
 
 ## Anti-goals
 
-* Dependency management - mise expects you to have system dependencies (like openssl or readline) already setup and configured. This makes it different than tools like nix which manage all dependencies for you. While this seems like an obvious downside, it actually ends up making mise far easier to use than nix. That said, we would like to make managing system dependencies easier where we can but this is likely going to be simply via better docs and error messages.
-* DevOps tooling - mise is designed with local development in mind. While there are certainly many devs using it for production/server roles which we support and encourage, that will never be the our focus on the roadmap. Building a better ansible/terraform/kubernetes just isn't the goal.
-* Remote task caching - turbopack, moonrepo, and many others are trying to solve this (major) problem. mise's task runner will likely always just be a simple convenience around executing scripts.
-* Windows support - I don't have a Windows machine and I think asdf/mise's focus on Unix tools will make supporting (non-WSL) Windows challenging if not impossible. Unless someone else wants to take on the challenge of building a Windows port I would not expect to see it happen.
+* Dependency management - mise expects you to have system dependencies (like openssl or readline)
+  already setup and configured. This makes it different than tools like nix which manage all
+  dependencies for you. While this seems like an obvious downside, it actually ends up making mise
+  far easier to use than nix. That said, we would like to make managing system dependencies easier
+  where we can but this is likely going to be simply via better docs and error messages.
+* DevOps tooling - mise is designed with local development in mind. While there are certainly many
+  devs using it for production/server roles which we support and encourage, that will never be the
+  our focus on the roadmap. Building a better ansible/terraform/kubernetes just isn't the goal.
+* Remote task caching - turbopack, moonrepo, and many others are trying to solve this (major)
+  problem. mise's task runner will likely always just be a simple convenience around executing
+  scripts.