search

newtheatre / history-project

:scroll: Historical record of happenings at the Nottingham New Theatre.
https://history.newtheatre.org.uk
MIT License
18 stars 14 forks source link

Expansion of the image / media archive #197

Closed wjdp closed 9 years ago

wjdp commented 9 years ago

Using our current storage solution shows can have a limited number of assets and photos. Shows usually produce many many more, along with other assets and occasionally video ( #71 ). Should this project endeavour to collect and archive all this material?

Sidenote: all the images/assets wouldn't be shown on a show page, just available under a 'more pictures' screen.

Technical Solutions

See #51 for usage constraints.

Git (and GitHub) is not suited for large files. An extension - git annex - provides tools to work with them. Large files are still 'in the repo' but they get physically stored somewhere else more suitable.

Cost

Service $/GB stored $/GB down Free Stuff
Amazon S3 0.022 0.05 5 GB of storage, 20,000 Get Requests, 2,000 Put Requests, and 15GB of data transfer out each month for one year
Backblaze B2 (very new) 0.005 0.05 10GB

Inflated numbers assuming shows have lots of images and some have video

X =
Number of image assets 5000
Average image size / MB 0.6
Number of video assets 30
Average video size / MB 300
Total / GB 12 (free-ish)

Due to the way the generation and caching works - a mixture of GitHub, Travis and CloudFlare - downloads should be near insignificant.

wjdp commented 9 years ago

Github has gone 1.0 on git LFS : https://www.youtube.com/watch?v=_11d1ZsEZ8g

wjdp commented 9 years ago

image

Also have put in an education discount request

wjdp commented 9 years ago

We now have 250GB storage!

wjdp commented 9 years ago

Now using SmugMug for photos and repo for everything else. Looking to migrate to Git LFS for posters and assets.