[x] renamed server files to camelCase for consistency
[x] added socket.io library for pushing tutorial changes from the browser to the server
[x] the tutorial builder now auto saves the tutorial state and stores it in Redis.
[x] save tutorial in github when submitting tutorial
[x] remove cached tutorial state when user deletes tutorial
Issue: #17 #113 #112
Reason
We want to autosave everytime the state of the tutorial changes because it improves the experience of creating a tutorial by the having the user not worry about unsaved changes and having to remember to save changes once in while.
It also cleans up the tutorial branches because we only commit when the user submits the tutorial for review. The button to update the tutorial state will also create commits for the branch which comes in handy when the user wants to make and push changes to a submitted tutorial.
Changes & Additions
v5socket.iolibrary for pushing tutorial changes from the browser to the serverIssue: #17 #113 #112
Reason
We want to autosave everytime the state of the tutorial changes because it improves the experience of creating a tutorial by the having the user not worry about unsaved changes and having to remember to save changes once in while.
It also cleans up the tutorial branches because we only commit when the user submits the tutorial for review. The button to update the tutorial state will also create commits for the branch which comes in handy when the user wants to make and push changes to a submitted tutorial.