We need a "one button" solution to the jupyterhub push, because it goes to three machines, and we would really like our internal users to do the pushes.
The problem is that updates often require changing version numbers/commits, e.g. radiasoft/containers@e412694, which I forgot to update before running the build. It would be cool if there was a Q&A (does warp need updating? Synergia? etc.) at the time of the push.
We need a "one button" solution to the jupyterhub push, because it goes to three machines, and we would really like our internal users to do the pushes.
The problem is that updates often require changing version numbers/commits, e.g. radiasoft/containers@e412694, which I forgot to update before running the build. It would be cool if there was a Q&A (does warp need updating? Synergia? etc.) at the time of the push.