You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A couple of lines in the readme on how to run my own copy of the calendar website wouldn't go amiss, so I can check that the trivial patch I just submitted didn't contain any hilarious syntax-error typos.
I'm guessing I have to do npm something, then run node on something obvious to anyone who's ever used Node before?
The text was updated successfully, but these errors were encountered:
erm. The reason that how to test it oneself is not documented is that the calendar is reliant on having a Google calendar back end; you can't easily take that away. So it won't run for ordinary people, and explaining how to set up a calendar and access tokens so that the code can use that calendar is not very useful.
However, this does point to the notion that we ought to have a "halfway house" mode which allows one to test a specific individual feed and print out the output from it, to confirm that an addition like this does the right thing. So let's leave this issue open and perhaps we'll get a chance to do that.
A couple of lines in the readme on how to run my own copy of the calendar website wouldn't go amiss, so I can check that the trivial patch I just submitted didn't contain any hilarious syntax-error typos.
I'm guessing I have to do
npm something
, then runnode
on something obvious to anyone who's ever used Node before?The text was updated successfully, but these errors were encountered: