Windmill

a year ago

Description: Self-hostable worker infrastructure, preconfigured to work out of the box.

Category: Automation

URL: https://railway.app/template/UI371k

5 Replies

a year ago

on the proxy service, you are using public hosts and ports, which will cause the user to incur double egress fees, I suggest using private domain and port reference variables.


a year ago

@brody great catch, thank you… i'll update accordingly.


mecattaf
HOBBY

a year ago

Hey @trogdor thanks for sharing this with us. I have deployed a windmill instance, and enabled public networking for the proxy module (caddyfile). even when using http i am getting a "not found" error

Image

any ideas on how to fix? thanks!


colincalnan
HOBBY

19 days ago

Hey, is there any way to spin up a worker with the chromium label so that I can run puppeteer?

https://www.windmill.dev/docs/advanced/browser_automation#puppeteer-bun


colincalnan

Hey, is there any way to spin up a worker with the chromium label so that I can run puppeteer?https://www.windmill.dev/docs/advanced/browser_automation#puppeteer-bun

12 days ago

  1. On Railway, duplicate your "worker" instance.

  2. On the duplicated instance, change the WORKER_GROUP variable from "default" to "reports".

  3. Assign the "chromium" tag to a job in Windmill.

    It will run on the new worker with the "reports" WORKER_GROUP variable.