add powershell wrapper for the Windows installer

[ebr]

proposal / for discussion

hoping :crossed_fingers: for a "pipe to bash" equivalent on Windows, to put this activity "on rails" such that there's less room for user error.

Requires testing by someone on a Windows system with antivirus enabled, in Powershell, by copying and pasting this command:

Invoke-WebRequest -Uri https://raw.githubusercontent.com/invoke-ai/InvokeAI/1acba80e6691b5b0a81377366228c9d9e8232f71/source_installer/Install.ps1 -UseBasicParsing -OutFile Install.ps1; .\Install.ps1

If that pans out, such command can be added to documentation, for a curl | bash -c -like experience (yuck, but it does help)

[tildebyte]

Requires testing by someone on a Windows system with antivirus enabled, in Powershell

I'm happy to try it, but I don't (and won't) use a 3rd-party AV

[tildebyte]

So far, so good, with a minor syntactical caveat:

Suggestion [3,General]: The command Install.ps1 was not found, but does exist in the current location.
PowerShell does not load commands from the current location by default.
If you trust this command, instead type: ".\Install.ps1".
See "get-help about_Command_Precedence" for more details.

retrying with the suggested fix works as expected

[ebr]

thx @tildebyte, I updated the command in the PR description. maybe we could ask someone in Discord to give this a try?

[ebr]

Not sure if it's still relevant, and I did ask someone in Discord to try it and they never did... But either way, this approach can be reused for the binary installer.

[ebr]

this is probably not going to be useful; closing and can reopen if we so decide