Stumpy has been updated to v1.4.
UPDATE: v1.4 and prior has a bug in short url lookups. v1.4.1 fixes this bug and should used over previous versions. See post here.
There are several fixes here which I will simple highlight as being numerous production setting bug fixes as well as a few visual updates and tweaks. Rolling Stumpy from Django debug mode to a production version run by way of fastcgi revealed a few bugs relating to redirects and submissions running into some problems with WSGI. These have been addressed in the latest set of commits and checking out version 1.4 from the GitHub page should give you something ready to roll non-development setting.
You can get this release here: https://github.com/mutaku/Stumpy/tree/v1.4
In this image you can see the main interface of Stumpy that is presented when you visit the root of your install. A bookmarklet button can be found at the top followed by some basic statistics as well as the most recent stumps and those that have been most utilized.
The following image shows part of the admin section for registered users that have been granted permission to access the stump section. This allows for viewing of all the details from the stump model, submission of a URL right through the interface, as well as sorting and viewing URLs through advanced filters or search. Remember, to submit a URL you must be logged into Stumpy as a registered user. You can add users through the root admin interface (not pictured).
I have included a sample Lighttpd stanza in the readme file that can help you setup your webserver to point to Stumpy. Simply edit this file to match your paths and make sure your webserver can run the fcgi script as well as access the socket paths setup in the stanza. You can then change your local_settings debug value to False. Just remember that any changes to files after the server has started won’t take effect until you have either restarted your webserver or the fcgi script. You will also need to have Flup installed for Django to use fastcgi. Lastly, make sure you have setup your FQDN in the sites section of the admin interface to ensure that links are displayed appropriately as several things use the domain read in from this value.