fly comparison

[gedw99]

fly has this also

https://fly.io/docs/blueprints/connect-private-network-wireguard/

The way the CLI works might help wush also in terms of userabilty and maybe some other ideas.

[coadler]

Hey! What features do you think would be a good fit from fly in wush? It seems a bit different since wush is just creating a "mesh" of Wireguard clients, rather than a server-based approach.

[gedw99]

Hey @coadler

I find fly not well integrated, because it's very much not idempotent. You have to do the commands in the right order etc.

They also keep changing stuff, but they endeavour to have errors show up in the Cli for deprecations.

In terms of features, and I have not used wush that much yet, it would be pretty awesome if your CLI has json out, so that I can do automation. So you can drive it.

The other thing is the fly cast network, which as you say is a server side thing. It allows you to connect to your Server in fly and "go inside" and be inside the linux of the docker you just deployed. The way you go inside is very cumbersome and defies doing any automation too, in that you cant just pipe command in from the CLI.
This of course is a big ask of wush..

The more I think about it, its like Fly is running the equivalent of wush in their proxies... Could be wrong, but it's sort of like that I think.

The other thing I tend to do is automate the crap out of CLI's using NATS jetstream. So NATS Jetzstream is acting as a command and control server. You send some command into nats and it will carry it out on 100's of Servers that are subscribed to that nats topic. It's just my own thing that I do, but I figured its worth putting it out there.

You can buzz m on telegram if you want to brainstorm ideas too !! It's on my profile.

Will be kicking the tires on wush today and so have more ideas :)