On Thu, Mar 26, 2026 at 5:30 PM Travis Briggs via Cloud <[email protected]> wrote: > One thing I'm not sure I understand, is it possible to run multiple > buildpacks/services from a single tool account? Or is tool/service a one to > one mapping?
Each tool only has a single hostname ($TOOL.toolforge.org) for webservice hosting. With manual Kubernetes adjustments it is possible to map that frontend webservice (Kubernetes Ingress) to multiple backend services, but there is not any tooling for this. It would be a very advanced topic to try and cover in a "beginner's workshop". It is possible to run multiple scheduled and/or continuous jobs from the same tool. It is possible to build multiple custom containers from the same tool. Those containers can be built from arbitrary publically accessible git repositories, including other Toolforge tools. > I was thinking it would be easier for all participants to share a tool, that > way we can all "become" the tool and see what the others are doing and > provide help and advice. It might be interesting to structure the event with teams of developers as practice for collaboratively working on tool maintenance. One way to do this might just be pairing folks off in teams of two or three and have them take turns pair programming style in running the keyboard during your exercises. Larger groups could certainly work too, but might be a bit more complex to structure exercises with more task distribution that would likely be needed for large groups. Bryan -- Bryan Davis Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis (WMF)]] irc: bd808 _______________________________________________ Cloud mailing list -- [email protected] List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
