Stumpy Version 1.5 is Now Available!

Stumpy Version 1.5 is now out and ready for testing.
Should be functional, but please submit any issues you might find to the issues page.

Changes include (from commits):

  • Removed hardcoded domains from JS. We now pipe in through the stumpy_domain var by setting a global JS var ‘DOMAIN’ in the index and then reference that JS var in our scripts. You will no longer need to set your domain as hard coded into javascript code.
  • Updated to use get submission of new URLs for shortening. This should work, but needs to be tested on the production version to make sure WSGI and such are working okay without the earlier hack that was implemented.

Stumpy Updated – v1.4.3

The Mutaku URL shortener, Stumpy, has now been updated to version 1.4.3.

You can find out more about Stumpy by clicking the first link in this post to read the initial write up on Mutaku, or you can go to the project page on Github.

Stumpy main page

This release includes a few small bug fixes as well as incorporating a new feature that, for logged in users, shows all of their submitted URLS at the bottom of the main page. Previously, this was only viewable by going through the admin interface. If you are not logged in, you will see the traditional view with the 5 most recent and 5 most visited URLs.

You get get the newest release at the Github page here: v1.4.3

Stumpy v1.4.1 – Critical bug fix

Stumpy has been updated to version 1.4.1 to fix a critical bug that was in all previous versions [Thanks, Erik!]. There was an issue with case-sensitivity in short url lookups that is now all patched up.

For general information on the newer v1.4+ Stumpy, see post here.

Get the newest, fixed version here.

Stumpy v1.4 – Grab it now!

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.

Stumpy main page

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).

Stumpy admin interface - stumps view

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.