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

deploy cellxgene in kubernetes #167

Closed
inodb opened this issue Jul 28, 2023 · 1 comment
Closed

deploy cellxgene in kubernetes #167

inodb opened this issue Jul 28, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@inodb
Copy link
Contributor

inodb commented Jul 28, 2023

Previously we have been able to deploy instances of cellxgene in heroku. See e.g.:

https://github.com/cBioPortal/brugge-singlecell

It alows one to point to an h5ad file in a bucket and deploy it. It would be great if we could deploy more cellxgene datasets on the cbioportal domain like e.g. *.cellxgene.cbioportal.org using our k8s infrastructure (or Fargate or some other AWS option, whichever makes sense). There is also this extension that allows one to use multiple datasets:

https://github.com/Novartis/cellxgene-gateway/tree/master

Using the cBioPortal domain would in addition allow mounting the tab inside of cBioPortal (this doesn't work atm because CORS is disabled on https://cellxgene.cziscience.com/)

Previously Jessica Singh from the Hyve used it and demo'ed its use. We've also had a server set up at single-cell.cbioportal.org but it is currently broken. We thought using the K8s infra or some other set up with auto ssl and all the bells and whistles might help with maintainability

@inodb inodb added the enhancement New feature or request label Jul 28, 2023
@inodb
Copy link
Contributor Author

inodb commented Nov 10, 2023

Fixed by @hweej : #170

@inodb inodb closed this as completed Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant