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

Better storage for supporting files #114

Open
jar398 opened this issue Oct 3, 2016 · 2 comments
Open

Better storage for supporting files #114

jar398 opened this issue Oct 3, 2016 · 2 comments

Comments

@jar398
Copy link
Member

jar398 commented Oct 3, 2016

The 'roadmap' says "Revisit our storage of files uploaded during curation, so that is easier to deploy the curation app to a new server." I didn't see an issue for this, so am creating one now.

Currently the files are in a directory inside the deployed webapp directory, and backed up nightly to varela.csail.mit.edu.

One problem with the current arrangement is that it makes replicating the front end server impossible - each replica would have its own copy of the supporting data files.

One option might be to move these files into the phylesystem. Another would be s3.

Some data:

  • There are currently 507 supporting files
  • The largest is just under 10 Mbyte
  • The total space used is 72 Mbyte

This issue might or might not be related to #111.

@mtholder
Copy link
Member

mtholder commented Oct 3, 2016

also related to OpenTreeOfLife/phylesystem-api#158

@jar398
Copy link
Member Author

jar398 commented Mar 14, 2017

also related: #126

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

No branches or pull requests

2 participants