[Task] Verify access to Gitea deployment from InnerEye workspace

[deniscep]

Story: #584

Verify that Compute Instance inside of InnerEye workspace can reach Gitea.

[msebragge]

@marrobi @deniscep

Gitea has a setting GITEA__server__ROOT_URL

Current value is https://gitea-cse-msr-dev.azurewebsites.net/gitea/

from internet https://cse-msr-dev.westeurope.cloudapp.azure.com/gitea works

from workspace https://gitea-cse-msr-dev.azurewebsites.net/ does not work since redirects go to
https://gitea-cse-msr-dev.azurewebsites.net/gitea/ (sign-in fails)

Changing the value to https://gitea-cse-msr-dev.azurewebsites.net/ fixes workspace access but breaks internet access.

It is possible to install gitea to a subfolder ie. https://gitea-cse-msr-dev.azurewebsites.net/gitea/ but that would require docker image changes go-gitea/gitea#3904

https://docs.gitea.io/en-us/reverse-proxies/#nginx-with-a-sub-path

Comments?

[deniscep]

@marrobi is there a requirement for TRE Admin to be able to add packages? If so, then we need to look into a long-term fix for this (@Lybecker, @christoferlof), but for now, @msebragge I would change the GITEA__server__ROOT_URL to be the internal URL and add InnerEye packages to the gitea through the bundle setup, which is run by the processor, so on the internal network.

[marrobi]

It is a requirement. We are already building a custom docker image so jus a case of replacing/modifying the nginx.conf in the dockerfile.

[deniscep]

Cool, let's then add it to the list and get it done! Since this is prio (otherwise Gitea isn't usable from the WS), let's pull it right in. @msebragge I've added the task for this #955