search

windmill-labs / windmill

Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal.
https://windmill.dev
Other
9.65k stars 443 forks source link

feature: a guide to get the cli into an air-gapped environment #1993

Open AudriusButkevicius opened 1 year ago

AudriusButkevicius commented 1 year ago

Currently getting the CLI requires installing it via deno, which by the looks of it calls out to the internet.

There is no explanation of how to bring that in into an air-gapped environment (also, not clear what the dependencies of the cli would be, do I need some runtime for it too or is it statically linked?)

sentry ships a statically linked cli which you can just bring in as a binary. Docker images are also fairly clear in what they are and how to bring them in, less so with deno.

rubenfiszel commented 1 year ago

@AudriusButkevicius I am a bit confused. In that air-gapped environment, you need to bring binaries and those binaries are installed from the internet at some point no ? How is that different from first installing deno, then doing deno install [wmill] ? Once it is installed, it won't call the internet but it will require a connection to your instance since it interacts with it

AudriusButkevicius commented 1 year ago

Agreed.

But I know nothing of deno, so it is not obvious how to do that, and I feel the docs should cover it.

If the binary is static, perhaps it could be provided as a separate download as a github asset or something, not requiring to install a separate package manager just to download a binary.