rubenf
rubenf11mo ago

what are you afraid of ? Windmill is very secure and has a tight permissioning model

what are you afraid of ? Windmill is very secure and has a tight permissioning model
16 Replies
rubenf
rubenf11mo ago
yes, they are running javascript under the hood actually we are thinking of providing windmill as a github action replacement by providing an integration with github ci also using worker groups with one worker per worker group you could target a specific worker to execute ssh in
sigcore
sigcore11mo ago
that's an interesting idea too, maybe someday I'll install windmill workers on every server to see what happens. It'd make it feel more like octopus-deploy or something similar
burakakca
burakakca11mo ago
How to fix Cors problem. I want to develop frontend while backend running on docker.
REMOTE=https://localhost REMOTE_LSP=https://localhost npm run dev

// https://localhost and https://localhost:3000 (https)
REMOTE=https://localhost REMOTE_LSP=https://localhost npm run dev

// https://localhost and https://localhost:3000 (https)
Caddyfile
localhost {
#reverse_proxy /ws/* http://lsp:3001
# reverse_proxy /ws_mp/* http://multiplayer:3002
reverse_proxy /* http://172.24.0.7:8000 { #docker ip
header_up Access-Control-Allow-Origin *
header_up Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
header_up Access-Control-Allow-Headers *
}
reverse_proxy /* http://172.24.0.3:3001 {#docker ip
header_up Access-Control-Allow-Origin *
header_up Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
header_up Access-Control-Allow-Headers *
}
tls ./cert.pem ./key.pem
}
localhost {
#reverse_proxy /ws/* http://lsp:3001
# reverse_proxy /ws_mp/* http://multiplayer:3002
reverse_proxy /* http://172.24.0.7:8000 { #docker ip
header_up Access-Control-Allow-Origin *
header_up Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
header_up Access-Control-Allow-Headers *
}
reverse_proxy /* http://172.24.0.3:3001 {#docker ip
header_up Access-Control-Allow-Origin *
header_up Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
header_up Access-Control-Allow-Headers *
}
tls ./cert.pem ./key.pem
}
caddy -v v2.7.5 h1:HoysvZkLcN2xJExEepaFHK92Qgs7xAiCFydN5x5Hs6Q= !image
Oleksandr Manakov
I've found a small mistake in Plotly docs. It references the ChartJs in the Configuration table
Plotly | Windmill
The Plotly component allows you to display a Plotly chart.
Alper
Alper11mo ago
I'm trying to use the helm chart and use a local Dockerfile for the worker image. is that possible?
rubenf
rubenf11mo ago
@Alper you can customize the image and anything would work as long as the image is available to the pods so you would probably need to publish it to a locally (to the pod) available container registry
Alper
Alper11mo ago
okay, never did that before. wouldn't it be better to allow custom Dockerfiles or is that not possible with kubernetes?
rubenf
rubenf11mo ago
kubernetes need to pass image references to containerd of the pods, so most likely no
Alper
Alper11mo ago
got it, thanks. will investigate how to add local registries via portainer then
Unknown User
Unknown User11mo ago
Message Not Public
Sign In & Join Server To View
rubenf
rubenf11mo ago
Yes we have confidential steps as an ee feature. Those steps get deleted after the full flow execution
Unknown User
Unknown User11mo ago
Message Not Public
Sign In & Join Server To View
rubenf
rubenf11mo ago
It's in advanced -> lifetime
Unknown User
Unknown User11mo ago
Message Not Public
Sign In & Join Server To View
rubenf
rubenf11mo ago
@HectorMalot it won't have any effect (normally)
Unknown User
Unknown User11mo ago
Message Not Public
Sign In & Join Server To View