public
Description: The software that currently powers jerakeen.org. Django-based, and rather messy.
Homepage: http://jerakeen.org/code/cougar/
Clone URL: git://github.com/jerakeen/cougar.git
jerakeen (author)
Thu Dec 03 04:58:19 -0800 2009
commit  fe3aec6500d7ed187bff71d3184d79e07da0f290
tree    4132ffe4207028c913a82a6894ea0981d5f216df
parent  14e957892745bc560300002b58ff3f7737eb8bea
cougar /
name age message
file Capfile Thu Sep 17 03:29:45 -0700 2009 deployment and docs changes. [jerakeen]
file README.markdown Thu Sep 17 03:32:08 -0700 2009 absolute links. [jerakeen]
file TODO Tue Sep 15 08:52:39 -0700 2009 make edit forms smaller, so I can see more text... [jerakeen]
directory cougar/ Thu Dec 03 04:58:19 -0800 2009 remove debugging [jerakeen]
directory lib/ Fri May 01 05:52:20 -0700 2009 junk a lot of old things. [tomi]
file manage.py Mon Sep 22 08:41:43 -0700 2008 vendor changes. [tomi]
directory mydjango/ Thu Sep 03 02:49:04 -0700 2009 make disuqs enabling a global config option. [jerakeen]
file passenger_wsgi.py Sun Aug 09 14:32:32 -0700 2009 mod_wsgi fix [jerakeen]
directory static/ Wed Jun 24 09:30:21 -0700 2009 sigh. Images. [jerakeen]
file template-cougar.conf Wed Jun 24 08:29:26 -0700 2009 Um. Yeah. What the hell, let's totally redesign... [jerakeen]
directory templates/ Mon Oct 05 09:47:42 -0700 2009 try resizing comment fonts. [jerakeen]
directory tools/ Wed Nov 25 01:43:15 -0800 2009 my thumbnailer is in a shipping container. [jerakeen]
README.markdown

jerakeen.org is normally powered by a hand-rolled CMS built with whatever bit of technology I happen to be playing with at the time. This month, it's built on Django, and I call this project cougar, for no real reason.

It's got multiple page types, so I can store my blog posts, code documentation, photos and external links in a single web application. All pages share a common tag cloud and you can get a view of all pages with a particular tag easily. Any of my pages can have thumbnail images, preview images, external links and uploaded files associated with them, and visitors can comment on any page on the site (this last one comes and goes according to whim and short-term philosophy).

The part I'm most proud of, however, is the photo and link syndication. Rather than put the photos into jerakeen.org itself, I use flickr and delicious to store photos and links, and periodically sync this data into jerakeen.org. I get all the benefits of using both flickr and delicious - powerful client tools, slick web interfaces, the social aspects - but also maintain a one-stop site that contains every piece of data I produce. I also sync the tags and comments from these sites, so my flickr tag cloud contributes to the jerakeen.org tag cloud.

I also syndicate my twitter, upcoming and Dopplr events into a lifestream page, where hopefully you can see everything I do on the internet.

Alas, the source code to this site is not properly released - I have neither the time nor the inclination to give it the level of flexibility it would need for other people to use it. Get Rails or Django and write one yourself - it's very easy. But if you really want the code, it's available in github. My syndication utilities are part of this project. Again, these are very specific to my install, and will require considerable tweaking to work for you.

I might provide help on installing cougar in your particular system, and I might accept patches that improve it, but I'm a fickle person, and will have changed CMS systems again in 6 months, so don't expect a formally maintained release any time soon..