Having to set up an SSH client and learn how to interact with resources via the command like is one of the most difficult parts of using Toolforge for new users. The API-oriented design work work going on at the moment opens up a new possibility: making it possible to maintain Toolforge tool resources (like jobs and web services) using a web-based interface built into Striker.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T332480 Make it possible to maintain Toolforge tools via an easy-to-use web interface instead of a command-line one | |||
| Resolved | dcaro | T332476 Toolforge: expose API gateway to the internet | |||
| Open | None | T332478 Decouple Toolforge API gateway authentication from Kubernetes certificates | |||
| Resolved | dcaro | T332479 Use Let's Encrypt certificates for the Toolforge API gateway | |||
| Open | None | T144713 Add a web shell allowing people to perform actions as their tool from striker | |||
| Resolved | Sarai-WMF | T375914 [Epic] Toolforge UI: Discovery | |||
| Resolved | Sarai-WMF | T381266 Toolforge UI: Publish newcomer experience and recruitment survey | |||
| Open | Sarai-WMF | T383146 Toolforge UI: Investigate integration of Striker functionality |
Event Timeline
Comment Actions
T144713: Add a web shell allowing people to perform actions as their tool from striker could be considered a duplicate of this or a specific implementation of the desired feature. For now I think I will make this task a parent to that older task and we can continue to explore what the "best" solution is to the general problem.