How to have a single Windmill act as a central space for multiple Windmill instances?
Hi, I currently have 1 self-hosted windmill container each running on 'n' different AWS EC2 instances (1 * n = n Windmill containers).
And I am finding this hard to manage since I need to visit each Windmill's URL individually (need to have 'n' different URLs/UIs) to trigger scripts/flows and view their states.
Is there a way (preferentially, out-of-the-box) where I can have 1 Windmill container coordinate with all my other instances. The central windmill container would have access to all my scripts/flows residing in other machines and serve as a single UI to manage everything. To clarify, I still want the scripts and flows to run in their own respective machines and the central Windmill instance would only help for triggering these scripts/flows and showing their states as if I was interacting with the individual instance's UI itself.
Is there a way (preferentially, out-of-the-box) where I can have 1 Windmill container coordinate with all my other instances. The central windmill container would have access to all my scripts/flows residing in other machines and serve as a single UI to manage everything. To clarify, I still want the scripts and flows to run in their own respective machines and the central Windmill instance would only help for triggering these scripts/flows and showing their states as if I was interacting with the individual instance's UI itself.
2 Replies
The way you are describing is exactly how Windmill is supposed to be hosted: one API server (UI) and one or more worker servers. You can host everything on one machine or scale horizontally having multiple machines hosting the workers.
The only requirement for that is that the workers and server must be able to connect to the same Postgres database.
You'd use then worker groups to keep the scripts and flows running on specific machines.
Hmm thought so too but new to this kind of configuration. Thank you!