option for more verbose output in the console for debbuging/testing/monitoring

[m040601]

I am starting to stress testing shiori for it's bottlenecks. Examples:

• When does it choke importing/exporting huge files ?
• When does it fails if the bookmark import files contain illegal characters ?
• How stressed is it with complicated queries ?
• Does it corrupt the database if power goes off ?
• Where is the bottleneck exactily ? Is it the sqlite read/writes ? Is it the main go application ? Is it the javascript speed in the browser ?
• etc ... etc...

To do this when I'm running "shiori serve" I can:

• "feel" how the browser is performing (use the browser performance tools)
• monitor my system CPU/disk/ram usage for peaks/stresses and bottlenecks.
• and most important, watch the console stderr/stdout for usefull information

It would be nice one could have an option or a flag, example --debug or --verbose or --warning --info --error to spit out more verbose information. Print it to this or that, pipe it to somewhere, logfile, errorfile etc.

Apologies for not contributing code. Again I'm not a developer, and I know nothing about Go programing.

[techknowlogick]

Don't be sorry at all, I really appreciate all of what your feedback, it is helping me a lot (with your feedback I've been able to fix several bugs already, and also it is shaping how I plan to make changes for the future).

Another project I am contributing to, has multiple logs that can be outputted, one is SQL commands being run, and another is webserver logs, I can try to integrate this into shiori as well. Perhaps I can also include outbound HTTP requests as well (for when bookmarks are cached).

[techknowlogick]

In the nightly I've added SQL logging to output and also webserver logs, perhaps those would be helpful in debugging.