-
Notifications
You must be signed in to change notification settings - Fork 24
Windows support TODOs #88
Comments
I just pushed code that will be in the next release to correct |
When I run
Hope this helps! |
I believe my issue is multipass is installed on windows (PS) and not WSL or bash |
@clarknelson Yup... Git Bash is required https://github.com/craftcms/nitro/blob/windows/README.md#installation |
I need to work on the paths for the apply command, path destinations are coming out strange on Windows:
|
@clarknelson yup resolved here and will be in the next beta release, early next week. #115 |
@jasonmccallister I'm sure you already know, but gotta "" those Windows paths take into account spaces. |
Great! I will start with Homestead and come back to Nitro when the new release is out :) |
I just pushed a fix for the windows |
I think the install script should ask you to add the nitro dir What the installer script does is essentially grab the nitro.exe from the latest release tag an put it in Windows support is still WIP since many commands don't run in Windows yet. |
thanks for the heads up on the path so I can keep going, devs say they will focus on windows support soon |
Where does it say it requires wsl to be enabled or gitbash as a pre-requisite? The commands runs only on cmd or powershell. |
@brandonkelly @jasonmccallister For windows there is still the need of php and composer installed as native for composer to work? |
Not really related to Windows, but no for PHP and the next beta release will have Composer installed in the Nitro machine by default (see #149).
Yes.
Yes, because of this:
We will update the docs on the windows branch as progress is made. Please note that Windows is still a WIP so there are issues we are working through in the beta. We plan to have official Windows support before 1.0 launches. |
We just released Nitro 1.0.0-beta.6 which greatly improves Windows support. Works with regular old cmd.exe, but the biggest caveats are 1) cmd.exe needs to be run with Administrator permissions and 2) installing/updating is a manual process. Be sure and check out the README for Windows-specific instructions. Going to go ahead and close this one out and we can keep track of Windows tickets separately in their own issues now. |
need native windows installer/updater (installer now works on git bash)
add/host command is broken because of sudo and different hosts path
The current solution works find in Cmder and Goland console, but cmd.exe is giving this:
interactive commands require j k l h keys to navigate instead of arrows (fixed by new prompt library)
redis command "Error: not supported by windows"
ssh command "Error: not supported by windows"
Figure out what to do with prompt library (make fork an official go module)? Because of Windows bugs among other issues.
Test our prompt library.
self-update
currently broken, but investigating fixssh
andredis
commands kind of work. You get a prompt, but no keyboard input is allowed.multipass shell
works fine from cmd.exe, butnitro ssh
has this behavior (regardless of ifnitro ssh
usesc := exec.Command(mp, "shell", machine)
or not)Uninstall instructions in readme
nitro remove
is broken on Windows.nitro-dev.yaml
The text was updated successfully, but these errors were encountered: