search

snapapps / edgy

a visual programming language inspired by Scratch
http://snapapps.github.io/
GNU Affero General Public License v3.0
51 stars 21 forks source link

Clickstream storage #199

Closed stevenbird closed 9 years ago

stevenbird commented 10 years ago

Investigate options for cloud storage of the clickstream, cf https://github.com/snapapps/edgy/issues/166

stevenbird commented 10 years ago

Investigate saving a browser session's worth of clickstream data to Dropbox.

Muon commented 10 years ago

The Dropbox APIs do not prohibit people with write permissions from overwriting arbitrary logs or even deleting them outright. Same with Google Drive. We may need a proper database for this.

stevenbird commented 10 years ago

We need to store logfiles which are plain text. I think a database would be overkill. Is there some way to set up an unreadable folder in which files have long names that cannot be guessed? This is possible with FTP. I don't mind funding a cloud-hosted FTP server for this. Please investigate possible solutions.

Muon commented 10 years ago

Folders can't be made unreadable to those with write permissions. Anyone could simply request the folder's contents to be listed.

JavaScript only lets you access HTTP servers, so FTP won't work, but we could easily make some sort of server to store logs on the filesystem.

stevenbird commented 10 years ago

Google will fund some cloud infrastructure, so please let me know what to select here: https://cloud.google.com/products/compute-engine/

aidanlane commented 10 years ago

Google will fund some cloud infrastructure, so please let me know what to select here: https://cloud.google.com/products/compute-engine/

Just noticed this comment. If you have any questions about Google Cloud Platform (compute engine, app engine, storage, datastore, sql, etc..), I may be able to offer some advise, as we use it for Alexandria. Cheers, A

Muon commented 10 years ago

Seems we'd want a Compute Engine instance to run a custom server for our log storage thing, and Storage for, er, storing the logs. I'd suggest first writing the server we'll use, though. Unless I've missed something and there's some way to effectively get a write-only logging bucket thing in one of the various storage options. @aidanlane Thoughts?