New feature for multiple-instance FeedLand

[scripting]

Previous versions saved pending confirmations in memory and on disk in stats.json.

This worked fine where there is one instance of feedland.js, but now we're scaling up so there can be many instances, all working on the same data.

This means we have to have the option to store pending confirmations in the database so all instances can work off the same data.

How to upgrade

If you want to convert your instance to use this feature, follow the instructions in the worknotes, here.

Changes

1. I updated the SQL setup instructions.
2. The new config option, flUseDatabaseForConfirmations, is documented here.
3. In the example config.json, I changed the value of confirmationExpiresAfter to 86400, 24 hours and flUseDatabaseForConfirmations to true. New installations should start out using the database for pending confirmations. No reason not to, every FeedLand has a database.

If you have questions, comments, problems -- post them in this thread.