Update repo name in installation script

[hsiaoyi0504]

As title, the change is straightforward.

[pcm32]

Hi @hsiaoyi0504 thanks for this. That script is actually quite outdated and we should probably remove it, but thanks for bringing my attention to it.

Are you trying to lift our Galaxy setup on your minikube/kubernetes cluster? I could point you to more up to date documentation on how to do this if this is what you want. Let me know what you're after particularly.

Thanks again!

[hsiaoyi0504]

@pcm32 Yes, I am trying to setup this. In fact, I think I was almost there, but it would be good if I can access to more up to date documentation. The steps I used are listed below:

• install minikube
• install kubectl
• minikube start
• Follow the command listed in install-phenomenal.sh

I would see that the service is running on my remote server, but I can't access it because it's in private network of the remote server (192.168.XXX.XX). I tried to do port forwarding, but it didn't work (or just I didn't do the right thing). I can see the service seems to run through X11, but I can't actually test it due to the network issue (My server is on another side of earth and X11 forwards the whole screen. Therefore, make it pretty slow ). Do you have any suggestion on this ?

Thanks !

[gabrielctn]

Hi @hsiaoyi0504 I maybe you didn't set the minikube docker environment variables eval $(minikube docker-env) ? I actually also ran into the same difficulties, here is the official more up-to-date documentation: https://github.com/phnmnl/phenomenal-h2020/wiki/QuickStart-Installation-for-Local-PhenoMeNal-Workflow And here is also a gist I made for myself, if it can help you: https://gist.github.com/gabrielctn/7f5e586fe0a900a879591dabe1fc26ca

[pcm32]

Hi @hsiaoyi0504 yes, please use the first or second link that @gabrielctn provided, all your steps where fine until the last one when using install-phenomenal.sh, which is highly outdated, and is replaced by the use of the helm repos.