This means doccelerator and my Tinderbox scraper that chucked stuff into a CouchDB for exposure by a modified bugzilla jetpack. Either couch went crazy or someone gave it a request that is ridiculously expensive to answer with a database the accumulated size of the tinderbox database. I’m not aware of any trivial ways to contend […]
Tagged CouchDB, doccelerator, review board, tinderboxAbout the name. David Ascher picked it. My choice was flamboydoc in recognition of my love of angry fruit salad color themes and because every remotely sane name has already been used by the 10 million other documentation tools out there. Regrettably not only have we lost the excellent name, but the color scheme is […]
Tagged CouchDB, doccelerator, docs, jshydraAs all misguidedly-lazy programmers are wont to do, I decided that it would be easier to ‘enhance’ CouchDB to meet my needs rather than to rewrite visotank to use SQLAlchemy. Also, I wanted to understand what CouchDB was doing under the hood with views and try my hand at some Erlang. CouchDB as currently implemented […]
Tagged CouchDBVisotank now allows you to select some authors of interest from a sortable list of contacts, and then show the conversations they were involved in. You get the previously shown sparkbars for the author’s activity. You also get sparkbars showing the conversation activity, with each author assigned a color and consistent stacking position in that […]
Tagged clicky, CouchDB, mailman, sparkline, visophyte, visotankFirst, let me say that Pylons with its Paste magic is delightful; lots of nice round edges helped me get something simple up and running in no time, and using genshi to boot. The new tool, visotank, is ingesting the python-dev mailman archives (as previously visualized) and putting them into CouchDB. The near-term goal is […]
Tagged CouchDB, mailman, sparkline, visophyte