Document the /clean/ endpoint on the index page
Update README.rst
Merge pull request #1 from mscherer/patch-1

Update README.rst
Update README.rst
Merge pull request #2 from mscherer/patch-2

Update README.rst
Make sure the connection is always properly closed
Rollback in case an error happens when committing to the database
Add Python metadata
Minor fixes to run faitout more easily

Missing configuration value, and virtualenv compatibility.
Fix the port, we use the default postgresql port
Add default port and host for the postgresql server in the config file
Propagate the port and host set in the configuration file to the backend

This makes sure the host and port are configurable and set correctly in the URL returned.
Make the maximum number of active connections allower per IP configurable
Clean the database should clean it rather than drop it

- This allows to reuse the same database multiple times
Finish separating cleaning from dropping

- Rename remove_connection to clean_connection
- Fix the call to clean_database
- Fix the returned message
- Create the drop_connection method
- Fix the call to clean_connection in the flask application
In fact cleaning is droping and re-creating
Output a little more information when something goes wrong
Drop all the connections to the database before dropping the db itself
Fix typos in the query to kill active connections
when cleaning the database it remains active