search

higlass / higlass-docker

Builds a docker container wrapping higlass-server and higlass-client in nginx
MIT License
32 stars 14 forks source link

Implicit ingest? #137

Open mccalluc opened 7 years ago

mccalluc commented 7 years ago

@pkerpedjiev : Thinking about how to make launch simpler, particularly if it may be coming from Refinery. I could imagine the system simply ingesting all files in the mounted directory by default on launch, and creating by itself a plausible default viewconf that references them all. Ingest is not instantaneous, so we probably also want some way of indicating through the UI that ingest has begun, but is not complete.

Thoughts?

pkerpedjiev commented 7 years ago

What happens if you run it twice in the same directory?

pkerpedjiev commented 7 years ago

Looking toward the future, I'm hoping to make HG work with data in an S3 bucket. Then we could either do away with the database or maintain a list of buckets in the database. Refinery would give HG permissions for the bucket and add it to the list known buckets. The viewconf would then use s3 paths rather than UIDs so it could generate a viewconf.

pkerpedjiev commented 7 years ago

For now, maybe running it in a new directory could do a sort of "sync" and only add files that are missing?