Confirm
656
edits
Changes
→Technology
* S3 is our backend
* MakeDrive is a few things:
** a node.js backend to proxy S3 requests using Webmaker auth. NOTE: MakeDrive does not (currently) deal with login, and assumes that users are logging in using Webmaker apps on another subdomain of *.webmaker.org (i.e., it uses a shared super cookie via the webmaker-auth npm module).** a way for logged in users to see their files via URLs (e.g., from AppMaker they can see their saved work in MakeDrive)
** a client-side library that mixes Filer, node/S3 communication, Webmaker auth, sync
* We need to sort out how MakeDrive integrates will integrate with makes.org for publishing (2 separate . The details of this are still being worked out, but probably it will mean copying data between S3 buckets , and allowing a URL like user.makes.org/folder/file to do what you'd expect and serve /folder/file from the MakeDrive. Longer term this probably means that user.makes.org/index.html is the first file you see/edit in your MakeDrive.* We need to figure out how to connect MakeDrive to the engagement/metrics workflow, especially so that we can watch for now)issues like rising S3 bills.
* The node/S3 proxy can use S3's API, and probably we can reuse an existing node.js module that does a bunch of this (knox?)
* Need to figure out push notifications so that S3 proxy can let local filesystem know when things are saved or changed. Probably [https://github.com/Yaffle/EventSource/ EventSource] (polyfill for [http://caniuse.com/#search=eventsource IE which doesn't support]) to do [http://dev.w3.org/html5/eventsource/ server-side events].
* On the client side we have to sort out things like rsync across the network divide (sockets? xhr?), VFS in Filer so you we can combine local and remote filesystems, and other dependent work.
==MakeDrive's Sync UX==
