crohr 4 days ago

I think if you want this submission to work, you really need to work on your getting started guide. Currently it just says: "Clone the repo".

With Forge, how long does it take to start a runner once everything is setup?

  • ebrilhante 2 days ago

    Very good point! I was so focused on building and eager to share the codebase that I ended up cutting corners on the documentation

    I did describe some of the details in this post: https://www.linkedin.com/pulse/forge-scalable-secure-multi-t...

    Fortunately, I’m working on proper documentation this week — it's finally getting the attention it deserves.

    Thanks for the nudge!

  • ebrilhante 2 days ago

    About boot times:

    Pod on an existing node (node already running other pods): ~1 minute Fast startup — just schedules the pod and initializes the runner.

    Pod requiring a new node (via Karpenter): ~5 minutes Includes provisioning the node, joining the cluster, and launching the pod.

    EC2-based cold start (no warm pool): ~5 minutes Similar timeline — launch instance, bootstrap the runner, and register it.

    Warm pool (EC2 or pod): Instant Pre-provisioned runners pick up jobs immediately.