-
Notifications
You must be signed in to change notification settings - Fork 14
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
Hosted file moved? #19
Comments
Yes, we will be slowing moving all our data to that host. If you want to absolutely protect yourself against data moves you could host genomes on your own server, but we don't move data often. |
Thanks @jrobinso |
Yes. But again, if this is an issue for your organization you might consider hosting the files you need within your organization locally, we host data for IGV as a convenience but it is not required you use our hosted data. Costs are becoming an issue and files could move again in the future. Some instructions are here: https://github.com/igvteam/igv/wiki/Hosting-Genomes Another important host, and I'm surprised IGV works at all without this one whitelisted is https://data.broadinstitute.org/igvdata Also, the following might well be used |
Thanks for getting this back.
The server(https://app.terra.bio/) we are developing is hosted by Broad. And I think all Broad hostnames are allowed. Thanks! I will also add that into our allowlist... |
Ahh, you are actually using https://github.com/igvteam/igv-notebook then. OK, sorry, my suggestion to consider hosting data on your own servers still apply, however the instructions I pointed to was for IGV desktop. What version of igv-notebook are you using? The most recent is 0.4.4, although for all practical purposes this is ready to release as 1.0.0. https://pypi.org/project/igv-notebook/ The configuration looks suspect, in particular the url and indexURL are not qualifed. I'm not sure how this is working, but if it was working before then the host name change might be the problem. I'm going to transfer this issue to igv-notebook. |
Actually we are using igv-jupyter https://github.com/g2nb/igv-jupyter which wraps igv.js by way of igv-notebook. |
OK. igv-jupyter is focused on the needs of the g2nb project, its not something I personally have any involvement in. I don't understand how those url property values are working but maybe it uses some magic of some kind. Anyway igv-jupyter project would be the place to discuss that. |
Hey @jrobinso need to reopen this issue again as we are broken by host move(and I suspect that is caused by this genomes.json updates). I checked this reference https://s3.amazonaws.com/igv.org.genomes/genomes.json and did see those two urls are now used by hg38. Thanks |
I don't understand question (1), but urls to data will change from time to time, these are not noted in change logs as they are not part of the application. As I suggested above you should consider hosting these files yourselves, if you want absolute control, we provide them as a service but it is not mandatory to use our (or UCSC's) hosted files. That said these do not change often. In the future we will be doing more direct references to UCSC hosted files, which will include the host you reference and possibly others in the UCSC domains. I had already list https://igv-genepattern-org.s3.amazonaws.com/ earlier. |
Thanks @jrobinso . For hosting our reference, we were thinking about that.
|
Yes that is what I recommend if you want full control over the URLs. Specifically do not use the "genome: id" shortcut, but fully specify everything. |
Hello, IGV.js is broken recently because
https://igv.genepattern.org/genomes/seq/hg38/hg38.fa.fai
is blocked by our Content Security Policy.It is expected because we have Content Security Policy allowlist and that allowlist does not contain that url.
IGV urls in our current allowlist are
I am wondering if igv.js recently move their hosted files to igv.genepattern.org?
I saw @jrobinso mentioned the moving here: igvteam/igv.js#1570 (comment)
but I am not sure if that is the same thing.
Thanks!
The text was updated successfully, but these errors were encountered: