wsl-vpnkit
nushell
Our great sponsors
wsl-vpnkit | nushell | |
---|---|---|
18 | 212 | |
2,035 | 29,485 | |
- | 4.0% | |
2.5 | 9.9 | |
4 months ago | 7 days ago | |
Shell | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wsl-vpnkit
-
Windows Subsystem for Linux 2.0 release
I'm going to wait a while to see how the new VPN stuff works out. Previously WSL2 didn't work with a Windows VPN without an extra tool ( https://github.com/sakai135/wsl-vpnkit ), hopefully this might fix things, but not going to risk trying it in case it breaks everything.
-
Simple PowerShell things allowing you to dig a bit deeper than usual
https://github.com/sakai135/wsl-vpnkit fixes that problem for me, and is less annoying than other fixes I tried
-
Make WSA (Windows Subsystem for Android) Run on Windows 10
If it works at all like WSL, you might want to look at wsl-vpnkit.
https://github.com/sakai135/wsl-vpnkit
It's not a proxy, but would give some idea how to shim into the middle.
-
Duality of man
there's a fix for that! https://github.com/sakai135/wsl-vpnkit
- Who else is forced to use Windows and how do you work around it?
-
Windows Subsystem for Linux (WSL) v1.0.0 released
Had similar issue. wsl-vpnkit resolved it for me. Very simple instructions to get it up and running.
-
Podman Desktop: A Free OSS Alternative to Docker Desktop
I had similar issues with a different VPN/Proxy at an earlier role. I solved with https://github.com/sakai135/wsl-vpnkit and trusting the root certificate of the proxy on the rancher desktop WSL2 vm (Assuming you're on Windows as I was).
Docker desktop pays for itself by solving these issues though IMO (I wasn't able to get a licence at the old role however)
-
How to share a vpn network connection to a container? (Noob alert)
If your host OS can connect to your company network, you can run docker on that host OS and have it hit the same network. I’m using docker w/ WSL2 and https://github.com/sakai135/wsl-vpnkit to accomplish this. It is, of course, more complicated than that, but that’s the general approach.
- Will Bun JavaScript Take Node's Crown
nushell
- Xonsh: Python-powered, cross-platform, Unix-gazing shell
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust.
That or https://www.nushell.sh/ which seems to be more interesting as it could be an equivalent to PowerShell for Unix.
-
jc: Converts the output of popular command-line tools to JSON
> In PowerShell, structured output is the default and it seems to work very well.
PowerShell goes a step beyond JSON, by supporting actual mutable objects. So instead of just passing through structured data, you effectively pass around opaque objects that allow you to go back to earlier pipeline stages, and invoke methods, if I understand correctly: https://learn.microsoft.com/en-us/powershell/module/microsof....
I'm rather fond of wrappers like jc and libxo, and experimental shells like https://www.nushell.sh/. These still focus on passing data, not objects with executable methods. On some level, I find this comfortable: Structured data still feels pretty Unix-like, if that makes sense? If I want actual objects, then it's probably time to fire up Python or Ruby.
Knowing when to switch from a shell script to a full-fledged programming language is important, even if your shell is basically awesome and has good programming features.
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Maybe if the "popular" shells, but http://www.nushell.sh/ is looking better and better
- "<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
-
jq 1.7 Released
Yeah agreed, especially now that PowerShell is available cross-platform.
Nushell[1] also seems like a promising alternative, but I haven’t had a chance to play with it yet.
-
The Case for Nushell
I also discovered an existing discussion[1] related to this topic which includes a link[2] to a "helper to call nushell nuon/json/yaml commands from bash/fish/zsh" and a comment[3] that the current nushell dev focus is "on getting the experience inside nushell right and [we] probably won't be able to dedicate design time to get the interface of native Nu commands with an outside POSIX shell right and stable.".
[0] https://gitlab.com/RancidBacon/notes_public/-/blob/main/note...
[1] "Expose some commands to external world #6554": https://github.com/nushell/nushell/issues/6554
[2] https://github.com/cruel-intentions/devshell-files/blob/mast...
[3] https://github.com/nushell/nushell/issues/6554#issuecomment-...
Today I learned (after disappearing down a rabbit hole after reading the linked article) that it's actually possible to begin to use & benefit from nushell's structured data pipe feature without changing one's current shell.
Structured data pipes have always been my primary reason for keeping an eye on nushell's development but after looking at the project's documentation again today it all still seemed "too much initial effort with uncertain outcome".
Because I don't want to switch my shell (not because bash is good but because it's not a priority to justify the expenditure of effort), I just want to have structured data in pipes within bash!
Turns out it's as easy as:
* nu --commands 'ls | where size > 1MiB'
(Where `nu` is the nushell binary being called from your existing shell prompt.)
Or, as more complete flow of data example:
* echo "[1,2,3]" | nu --stdin --commands 'from json | to json' | cat
Now you can fit nushell within your existing workflow where ever it's useful enough for you--without needing to commit to changing your entire shell.
(And this isn't the only or necessarily the best way to arrange things for the communication with bash--there's "^" & "externals" & "command signatures" & "from ssv" etc too.)
And nushell does have some nifty tools such as `explore` with `:try` to interactively build a processing pipeline.
But this information doesn't seem to be documented anywhere in the "book" or other introductory material. It only seems to be documented in the help message of the `nu` binary--which I almost didn't even get as far downloading today.
But then I found the help text in the source, so decided to try it again: https://github.com/nushell/nushell/blob/fd4ba0443d01e67f6304...
If the structured data pipes is one of the main appeals for you, maybe try this approach out?
What are some alternatives?
fish-shell - The user-friendly command line shell.
elvish - Powerful scripting language & Versatile interactive shell
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
genie - A quick way into a systemd "bottle" for WSL
PowerShell - PowerShell for every system!
alacritty - A cross-platform, OpenGL terminal emulator.
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
volta - Volta: JS Toolchains as Code. ⚡
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
gvisor - Application Kernel for Containers
UTM - Virtual machines for iOS and macOS
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]