RI can just tell you it works and it's used in production by us: https://github.com/windmill-labs/windmill/blob/26822d9db8bcf91d191cbfe2f1fc38d7e0bd4670/frontend/src/lib/components/details/utils.ts#L54 ¯\_(ツ)_/¯
GitHub
Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool. - windmill-labs/windmill
Nhow can you make docker containers running on Windmill access the same networking as the rest of the Windmill services?
I added a redis instance to the docker compose file. I have a Python script running on Windmill that accesses this redis instance successfully
I have a docker container running after I followed the documentation on how to setup docker. The script to run it is as follows:
I get the following error (container running JVM code):
This means that my code inside my container was not able to resolve that redis = my redis instance, but the python code was able to.
I added a redis instance to the docker compose file. I have a Python script running on Windmill that accesses this redis instance successfully
I have a docker container running after I followed the documentation on how to setup docker. The script to run it is as follows:
I get the following error (container running JVM code):
This means that my code inside my container was not able to resolve that redis = my redis instance, but the python code was able to.
NI tried adding a network to the docker compose and connecting the worker and redis, but that caused the worker to be unable to execute docker commands
Kwouldnt CORS apply to both widgets?
R@Kelora not necessarily since the origin domain is different but i'm not a cors expert
RI can just tell you that pdf on external domains on app.windmill.dev do not work because of CORS
Kok gotcha
NSo I ended up just hosting my own redis on a remote VM as a solution, but I wish I was able to connect to the local redis instance
TWhen you connect via python, you're connecting from within a WM worker that has access to the internal Docker network.
When you connect using the
When you connect using the
docker run, you're running a docker client that lives inside the worker, and this client is connecting to the host system, therefore, if you want to connect from there, your have to expose the redis container to the host.
Nyes, thanks, I am aware of the DIND situation. I experimented with different configurations to expose the custom image to the docker-compose network but couldn't manage to make it work. Some network configs made the container hang up indefinitely without any error logs.
My devops friend suggested I could "flatten out" the network topology with K8s but I decided that the extra time was better spent on setting up a remote redis instance instead and making it an API. that beign said it's less secure as securing redis over the internet isn't trivial
My devops friend suggested I could "flatten out" the network topology with K8s but I decided that the extra time was better spent on setting up a remote redis instance instead and making it an API. that beign said it's less secure as securing redis over the internet isn't trivial
TOh, that's weird
Kmight be completely k8s specific but has anyone used gpu accelerated windmill workers? havent tried to implement it myself yet but I assume that's possible
RYes we have customers doing that
Kand they don't count as vCPUs in the EE licensing?
K(beyond the CPUs used by the workers)
RThe GPUs themselves no
Kok ty
DIs there a way to use native mysql scripts with listy inputs? For example
where iso2c IN(:input) where :input is more than one value? Or maybe a better way of asking is what sort of operations do those scripts support, since I've gotten some unexpected behavior out of them once or twice.RWindmill simply use prepared statements, so anything that is supported by msql prepared statements will work, and anything that isn't won't.
Dahhh okay. That explains why a few things like trying to pull shenanigans with stored procedures worked in a SQL browser but not those. Thanks.
HHi @mbaum! You can use webhooks that are generated for every deployed scripts and flows https://www.windmill.dev/docs/core_concepts/webhooks
Webhooks are a way to interact with Windmill using standard web technologies.
R@Craig can you give me the job id
Ron it
RHi @paul , if you can write the schema as a result of the last job, we can add support for picking it up from there
RAnd currently no you cannot embed an app as an approval form but we're thinking of adding it as a feature. Most likely, it will be app embedding a flow that has approval steps
HHi @Steve CL ! Sorry I'll clarify the docs & Pricing page asap
As the AI suggests, using BigQuery in itself does not require an Enterprise license since you can just create a BigQuery resource and use from scripts in TypeScript, Python etc.
However, the BigQuery runtime, available as a native script language in Windmill, is under Enterprise (or cloud plans) license
In other words: nothing forbids you from interacting with BigQuery in Windmill community edition, it's just the BigQuery runtime that is under Enterprise Edition for more convenience
As the AI suggests, using BigQuery in itself does not require an Enterprise license since you can just create a BigQuery resource and use from scripts in TypeScript, Python etc.
However, the BigQuery runtime, available as a native script language in Windmill, is under Enterprise (or cloud plans) license
In other words: nothing forbids you from interacting with BigQuery in Windmill community edition, it's just the BigQuery runtime that is under Enterprise Edition for more convenience
RApologies, we will improve our documentation. The expectation would be that you're inside a VPC and do not expose 5432 past your ingress, it's just a way to connect from the rest of your VPC. As to changeme being the password, we can re-iterate that it is meant to be changed in the self-host doc
RThank you for the feedback. Wrt to documentation, it's also open-source so if you're up for it, you could even do a contribution with the notes around security, otherwise I will do it later this week: https://github.com/windmill-labs/windmilldocs
GitHub
Contribute to windmill-labs/windmilldocs development by creating an account on GitHub.
Rbut yes, in general, you should always secure your VPC and never expose 5432 to your ingress, and I mean VPC ingress by that. The large majority of production use is through AWS/GCP/Azure and that's the default there wrt to the VPC Ingress/Load balancer/etc