#Wush via Powershell

42 messages · Page 1 of 1 (latest)

fierce flume
noble hamlet
#

you don't, what you are basically asking how to a person is supposed to understand chinese when they are only speaking english.
Curl is a third party tool and has nothing to do with powershell in general either. At some point curl was an alias for the cmdlet invoke-webrequest that works differently with different parameters etc.

#

bash (sh) is a different shell all together from what powershell is.

#

you can rewrite the script in powershell but why bother doing that when you can just run in an supported environment...?

fierce flume
#

Oh, you mean that Wush is not intended for Windows?

#

I thought this also, initially, but then, I saw this in the latest releases area:

wush_0.4.0_windows_amd64.zip

#

So, that made me think that it must be supported in Windows also.

#

So, I downloaded the zip and click the exe file.

#

Nothing happened.

noble hamlet
#

I'm not saying it is not intended for Windows. I'm saying that the install.sh script is not intended for Powershell.

fierce flume
#

I don't even see a process in Task Manager or anything titled wush via get-process -name *wush*

noble hamlet
#

The install.sh assumes you'll use that script on windows using mingw etc.

#

How the tool itself is supposed to work and how is something you'd need to consult their documentation for.

#

But that documentation will typically only apply if you have installed it as intended.

fierce flume
fierce flume
noble hamlet
#

Once you've installed the tool as they expect it will probably work as intended.

fierce flume
#

The documentation says to read the "latest releases" for manual install, but I didn't see any instructions there.

#

Maybe, they were referring to the install.sh page you referenced.

noble hamlet
#

They assume you know that you need to use a bash shell of some sort to run the install.sh

#

The install script might work also under WSL.

#

How the tools is supposed to work and how you execute is something you'd need to ask those who know the tool.

fierce flume
#

Ok, thank you.

raven cedar
#

Seemed like you solved this maybe, but do you know if this is better for file transfer than LocalSend?

brazen epoch
#

Wush is based on Wireguard (via Tailnet), so it's not local-only like AirDrop/LocalSend

#

The choice of using a bash install.sh script cracks me up though. Why is a go app using a "installer"? Turns out it's just a downloader ... except on POSIX platforms it trying to sudo setcap cap_net_admin ... so it can change the size of the UDP packets.

You definitely do not need the install.sh (especially on Windows).

#

For what it's worth, if you have Install-GithubRelease you can use it instead, and if you don't, you can install it with Install-Script 😉 but on Linux/MacOS, you'd want to set the permissions by hand:

Install-Script Install-GitHubRelease
Install-GitHubRelease coder wush
if ($IsLinux -or $IsMacOS) {
  sudo setcap cap_net_admin=eip $((get-command wush).path)
}
raven cedar
#

I love LocalSend for cross-platform "AirDrop" it's really fast and easy

fierce flume
brazen epoch
#

It runs, gives help, I haven't actually used it to do anything

fierce flume
cobalt tree
#

works fine for me

#

just used it and transferred file windows to windows

cobalt tree
fierce flume
#

I'm not sure what I did incorrectly in the steps I listed above.

cobalt tree
#

You double clicked the exe, right?

#

You have to go to cmd line and run wush.exe serve

#

That starts the server