Make usage of Toolforge more familiar to users of commercial Platform as a Service (PaaS) products (Heroku, DigitalOcean, Google App Engine, etc) by implementing a Container based PaaS product that provides "build pack" and "push to deploy" workflows for deploying and scaling Tool owned processes.
Beta rollout
We have started a beta with the process outlined in {}, this is the current timeline:
[30th June 2025 - 28th February 2026] Start the beta and implement missing features
- Announce to the community including
- Documentation
- How to use the new features
- How to give feedback and how we are going to handle it
- Documentation
- Gather feedback from users
- Fix bugs that might arise
- [every 2 weeks] Check-point for direction/summarize feedback to date (2 weeks after start, 2 weeks cadence, at least 7 cycles - 3.75 months)
- Decide and implement a round of new features
- Iterate if needed
[1st March - 30th June 2026] Stabilization phase (duration 4 months)
- Fix bugs + stabilization features
- No big changes to existing features
- Refine and iterate on the backwards compatibility process and flows
[1st July 2026] Release as stable
- Regular development cycle, stable features now fully under the backwards compatibility processes
- Upload the tool config schema to https://github.com/schemastore/schemastore/
Latest update: 2025-10-22
See also
- Current user documentation:
- Current admin documentation:
- Original proposal: https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Toolforge_push_to_deploy
- Design Documentation: https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Toolforge_Buildpack_Implementation