Added a simple route response and some testing
Merged
requested to merge 14-launch-endpoint-no-auth-no-params-return-path-also-test-jupyter-use-case into develop
Beginning with 2nd June, only the "Single Sign On" option for login to the GitLab web interface will be possible. If you don't have an MPCDF wide second factor so far, please get one at our SelfService (https://selfservice.mpcdf.mpg.de). The GitLab internal second factor will not work.
Draft for #14 (closed) I want to return a link for us to test through the proxy once the proxy CI building and pushing to registry is done. #13 (closed)
Other than please bring whatever design choices you have in mind. I am also using a 503 HTTP response. Will you prefer that or something else if all container 'routes' or lets say instance allocation slots are taken?