fork/cellxgene-gateway
1
0
Fork 0
mirror of https://github.com/Novartis/cellxgene-gateway.git synced 2026-10-10 16:20:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

added a future work section

Alokito
2019-09-16 14:58:07 -04:00
parent a6d34902d8
commit 4a578dc218
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Home.md
+9 -1
@@ -7,6 +7,7 @@ This page describes the concept and architecture of the Cellxgene Gateway
* [Class Structure of Gateway](https://github.com/Novartis/cellxgene-gateway/wiki#class-structure-of-gateway) * [Class Structure of Gateway](https://github.com/Novartis/cellxgene-gateway/wiki#class-structure-of-gateway)
* [Subprocess Backend](https://github.com/Novartis/cellxgene-gateway/wiki#subprocess-backend) * [Subprocess Backend](https://github.com/Novartis/cellxgene-gateway/wiki#subprocess-backend)
* [Docker Backend](https://github.com/Novartis/cellxgene-gateway/wiki#docker-backend) * [Docker Backend](https://github.com/Novartis/cellxgene-gateway/wiki#docker-backend)
* [Future Work](https://github.com/Novartis/cellxgene-gateway/wiki#future-work)
# Overview # Overview
@@ -121,4 +122,11 @@ In theory, to support Docker we need the following changes:
* The <pid>.txt files should become docker information files named after some container identifier provided by AWS * The <pid>.txt files should become docker information files named after some container identifier provided by AWS
* The files should be stored on the cellxgene EFS (shared filesystem) instead of in /tmp. * The files should be stored on the cellxgene EFS (shared filesystem) instead of in /tmp.
I'll let you know how it goes in practice if we ever get to it 😄 . I'll let you know how it goes in practice if we ever get to it 😄 .
# Future Work
In addition to the Docker backend, there are a couple things that would be nice to clean up if this continues to be used,
* The current implementation expects all datasets to be available on a mounted file system. It would be nice to allow it to use files from S3 or other kinds of file/object stores.
* Customizing the look and feel of the front end is rather messy at the moment. Adding a mechanism to override the Jinja templates may help.