Store the code blob in s3 rather than in MongoDB

[ianjennings]

• Configure a .env file to include AWS key and secret
• Create a "signed upload URL on the server"
• Pass the URL to the client
• Allow the client to upload the javascript
• Store the location of the JS on the server

Simple tutorial here
https://softwareontheroad.com/aws-s3-secure-direct-upload/

Things that need to be uploaded:

• Custom test code
• Custom plugin source

Things stored in db:

• Babel configs

[wlawt]

Related to #25 and will close the issue

[wlawt]

Moving to Milestone 2 since we'll be discussing the tradeoffs between MongoDB and S3, and the use cases where each will be needed.

We can start implementing this next week.

[wlawt]

We'll still be using S3 for the plugins and input code as mentioned in today's post-retro

[mohammedsahl]

To be clear, the code that stores the source/plugin/configs into an S3 bucket lives on the client side, correct? @kirbygit and I were a bit confused since there is a Server label
@wlawt @ianjennings

[wlawt]

@kirbygit showed me a quick snippet of his code - it looked like he used express.js and was going to transfer it to sails.js.

I believe the goal is to just return a URL back to a client, so it can exist as an endpoint in the server, or if it can all be done using Axios in the front-end that works, too!

cc: @ianjennings