Improving error reporting in Canopy

[abbysmal]

Hello,

Following the mailing list report, I was thinking about how we could improve error reporting in Canopy when it tries to pull new content but fails to do so (with, for example, an invalid Canopy file that will be dropped).

Solution I thought about:

• Storing the failing file and displaying it on the site too (or displaying it only with a specific get parameter ?), with the error written in the page's body ?
• Having an offline command line utility to check if a file is good ?
• Having a page displaying git pull's logs and errors ? Page that could be hidden (by using somehow the secret webhook URL ? Or a specific param ?)

What do you think about those ideas ? Any better one in mind ?

[abbysmal]

(the offline command line utility also somehow joins some terrible scheme where we could also allow Canopy to generate actual HTML files statically like any static blogs generators. Not sure we want to do that but that could be also possible.)