Open jlord opened 11 years ago
Goals/intended workflow of Sheetsee-cache as a command line node module.
sheetsee init <spreadsheetkey> <filename.html>
to initialize a full instance of sheetsee; this includes building out a directory for required libraries and making a .html file with the minimum elements for getting started.
sheetsee update
will force a fetch of the latest data from the spreadsheet and overwrite the existing spreadsheet data
sheetsee expire <miliseconds>
set an expiration data for your data upon which time a request to your .html file will trigger fetching new data. this defaults to never expire.
also
sheetsee <spreadsheetkey>
to write data from spreadsheet to a file in current directory without starting an instance (basically, just a transform of your remote spreadsheet data into json saved locally).cc @SaraJo - realized this wasn't as quick of a project as I initially thought. Want to also get your thoughts on what the module should do.
cc @maxogden in case i forgot something
Why does there need to be a copy of the spreadsheet serverside? Can you not make a request from the server? Is is it a cross domain limitation?
Asking for context purposes.
The purpose of the copy on the server is because sometimes going to Google to get the data can take a while*. Storing it on your server eliminates that step and means your page will probably load faster.
So that you don't have to edit server.js to set the expiration time or spreadsheet key.