bump version of django-gevent-deploy to see if a new gevent fixes the weird resource leak slowdown. Straws, people clutching.
no, it just randomly broke django-compressor. YAAAAY
updatefabfile for new server
Add second copy of the homepage view so that we can investigate why the homepage and nothing else has a resource leak
remove all editorial content from the not-a-homepage. This is really dumb.
Homepage with content has a resource leak, homepage without content doesn't. LET'S BINARY SEARCH THIS SUCKA
try without the news
try wit just the news
news again, but with a minimal template
and now without markdown
see if markdown without scrubber is any different
https://github.com/waylan/Python-Markdown/issues/161 suggests that nl2br is a bit dodgy. let's see.
Right. It would appear that markdown has a resource leak, so create a new instance of it on every call rather than keeping a global instance.
Aha! Apparently I *can* have a persistent Markdown interpreter, I just have to call reset() on it
Add maintenance report 'prods without platforms'
Fix dir entry regexp so that it doesn't break on entries with a numeric username (which have extra spaces before them)
filter deleted directories out of compofolders listings
add report of dead amiga.nvg.org links
let's fix that report title, mmkay?
and let's update the internal report name too