Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that the current /go-cam web app can operate through the root domain proxy #965

Open
kltm opened this issue Dec 20, 2018 · 12 comments

Comments

@kltm
Copy link
Member

kltm commented Dec 20, 2018

Currently, the /go-cam web app at geneontology.cloud does not work well with the proxy; ensure that the current /go-cam web app can operate through the root domain proxy.

Originally noted in #959 (comment)

If this turns out to be onerous, we can use a temporary redirect in the interim.

@lpalbou
Copy link
Contributor

lpalbou commented Dec 20, 2018

It's possibly be due because the go-cam site is a SPA, hence every redirects should be sent to the index.html ?

@kltm
Copy link
Member Author

kltm commented Jan 22, 2019

Now using forwarding until proxy fixes in place.

@lpalbou
Copy link
Contributor

lpalbou commented Feb 20, 2019

@kltm do we close this ticket as it's working for the moment ?

@kltm
Copy link
Member Author

kltm commented Feb 22, 2019

This is for removing the .cloud extension by making it work via the proxy. There is another ticket (around here somewhere) which was just putting the forwards in place for now.

@pgaudet
Copy link
Contributor

pgaudet commented Feb 25, 2019

@kltm low priority / not planning to do this for Cambridge

@lpalbou
Copy link
Contributor

lpalbou commented Aug 15, 2019

I assigned @kltm to this issue since it's the geneontology.org proxy he manages.

Any route /gocam/* must redirect to http://geneontology.cloud/*

It should be easy as we only have 3 routes:

@kltm
Copy link
Member Author

kltm commented Aug 15, 2019

@lpalbou Now worries as it is not immediately scheduled, but the breakage is occurring in your app, as we found during the initial attempt. When this becomes a little more immediate, we can retry and better document what does wrong or another fronting proxy can be made to simulate.

@lpalbou
Copy link
Contributor

lpalbou commented Aug 15, 2019

I don't think this is coming from the app, I can deploy it under different domain names and it still works so all links are relative.

However, it's a SPA, so all routes must target the geneontology.cloud/index.html (#965 (comment)).

If you have some logs or examples during your initial attempt, we can look into it. Thanks

@kltm
Copy link
Member Author

kltm commented Sep 25, 2019

@pgaudet Assuming this is bumped up for geneontology/geneontology.github.io#180 ; not sure why I can't add this to related project--my list seems to be limited. Perhaps you'd have better luck?

@kltm
Copy link
Member Author

kltm commented Sep 25, 2019

Picking up from gitter.

Unfortunately, the log files for the test are likely long since rotated away. On the upside, we can start building up again on the test configuration or just work it out in a docker image.
The basic test configuration is here:
https://github.com/geneontology/operations/blob/master/ansible/root-domain-head-up-test.yml , via https://github.com/geneontology/operations/blob/master/ansible/roles/webserver-apache-proxy-full/templates/proxy-80.conf .
This is the main proxy from the apache server to the https github-delivered pages. Currently, the /go-cam path just redirects. What we'd probably need is likely another proxy on the /go-cam path to deliver your application.

@kltm
Copy link
Member Author

kltm commented Sep 25, 2019

Ah, found the last branch for this work: https://github.com/geneontology/operations/tree/issue-go-site-965-go-cam-cloud-proxy

@lpalbou
Copy link
Contributor

lpalbou commented Sep 25, 2019

Do you remember the type of error / problem you had ? It would be helpful.

Unless you have a better suggestion, I will setup a basic apache server with my geneontology.xyz to see what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants