Add BackBlaze Functionality

[DanielBatesJ]

Also figure out exactly how to handle the work-flow from moving the uploaded file from the front-end user, to the backend web-server. Rename (and parse?) the file, and upload or reject depending on results.

• [x] Pass file to webserver
• [x] Accept the file
• [ ] Parse the file
• [ ] Rename the file
• [x] Pass to *BackBlaze
• [ ] Allow for batch downloads (download all demos from one user)

[DanielBatesJ]

Update, we are considering storing the demos on backblaze now, will need to interface with their API, and store new demo data based off of the file_ids in backblaze.

[Naleksuh]

@DanielBatesJ Is there any reason they can't be stored on the site rather than having to use a third party service?

Also, can you clarify if this repository is currently in use on board.portal2.sr or is a work in progress? (Just found this so I'm not sure, sorry)

[jonese1234]

@Naleksuh Current demo amount is too large to be held on web server. Currently around 50gb and growing.

This is the new site.

https://github.com/p2sr/Portal2Boards is the old/current one.

[DanielBatesJ]

Paying for additional file/block storage on a vm instance is significantly more costly than holding it in some cheap mass storage solution. The speed advantages are also negligible. The current plan is to migrate the existing demos over to BackBlaze and to use that going forward on both the current boards (as Jonese linked above) and the new boards.

[DanielBatesJ]

Now we're switching off BackBlaze. This will need to be updated with the steps required to work with Hetzner storage.