Work: couchdb javascript melbjs nodejs presentations shinetech
by Cliffano Subagio
1 comment
Node.js Presentations
I gave two Node.js-related talks within the past week.
The first one was titled “From Java To Node.js”, at Shine Technologies‘ developers meeting on August 5th, 2011.
The second one was titled “JavaScript Everywhere From Nose To Tail”, at Melbourne JavaScript usergroup on August 10th, 2011, with Carl Husselbee from Sensis.
Happy with the positive feedback from the audience of both talks, thanks folks, much appreciated!
Update (08/09/2011):
And here’s the video from the second talk…
JavaScript Everywhere – From Nose To Tail from Benjamin Pearson on Vimeo.
Couchtato Introduction
Last Thursday I put up a post at Shine Technologies blog titled Couchtato – A CouchDB Document Utility Tool Written In Node.js. It’s a short introduction to Couchtato, a little hobby project I worked on over several evenings and lunch breaks.
Do check it out if you are a CouchDB and NodeJS user.
Running CouchDB-Lucene On Tomcat
As of the time of writing, CouchDB-Lucene (v0.6.0) distribution was bundled with Jetty WebServer and runnable from command line. But if you dive a little bit into the code, you’ll find that the run script basically executes com.github.rnewson.couchdb.lucene.Main, which in turn (1) reads the couchdb-lucene.ini config, (2) creates a Jetty Server, and (3) sets up com.github.rnewson.couchdb.lucene.LuceneServlet on the server.
At work, we had to use Tomcat due to SOE reason, so I spent a bit of time trying to get CouchDB-Lucene running on Tomcat and get it deployed as a .war file. Here’s how we did it, please note that this is the tedious way of doing it, all because I had to integrate CouchDB-Lucene into an existing web app. There’s an easier way to build a .war file mentioned at the end of this post.
- Unpack couchdb-lucene-<version>.zip .
- Create a standard web app directory structure with WEB-INF dir.
- Configure LuceneServlet in your-app/WEB-INF/web.xml .
<web-app> ... <servlet> <servlet-name>lucene</servlet-name> <servlet-class>com.github.rnewson.couchdb.lucene.LuceneServlet</servlet-class> </servlet> ... <servlet-mapping> <servlet-name>lucene</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> ... </web-app>
- Copy all jars from couchdb-lucene-<version>/lib/ to your-app/WEB-INF/lib/ . The jetty-*.jar files can be excluded.
- Copy couchdb-lucene-<version>/conf/couchdb-lucene.ini and couchdb-lucene-<version>/conf/log4j.xml to your-app/WEB-INF/classes/ .
- Deploy your-app on Tomcat.
- Configure the CouchDB external process hook script with the host name and port number where Tomcat is listening on.
There was one catch though, LuceneServlet did not have any no-argument constructor for the web.xml configuration, so that’s one of the changes I had to make. The other change was some file reorganisation so that you can use mvn war:war to generate a target/couchdb-lucene-<version>.war file. Too easy!
I’ll submit a pull request to master later, but in the mean time you can clone my fork to get the patched LuceneServlet and to easily generate the .war file.
Update (27/05/2011): It’s now part of couchdb-lucene master as of 0081272a30dc679effc1cf1298e365b953f568a5, should be included in v0.7.0 .
CouchDB Upgrade From 0.11.0 To 1.0.1
This post also serves as a note to self when I do another upgrade in the future.
It’s still not clear to me of what’s the best practice for upgrading a CouchDB installation. From the mailing list, some people suggested backing up the config and database files, uninstalling the old version, then installing the new version. But, really, what’s involved in uninstalling a CouchDB installation? manually deleting the files from the old installation? I had the same confusion when I tried to do the upgrade on OS X, once from a compile from source, and another from a CouchDBX installation.
So instead of ‘the best practice’, I’ll just share what worked for me. I simply installed the new version using the same way as when I installed the old version, i.e. compile from source, and the files from 1.0.1 installation overwrote the files from 0.11.0 . Here’s what I did:
- I searched for CouchDB config and database files, and found them in /usr/local/etc/couchdb/local.ini and /usr/local/var/lib/couchdb/mydatabase.couch . I then backed up those files.
- The fact that I found those files under /usr/local indicated that I must’ve used –prefix=/usr/local when I installed 0.11.0 .
- I downloaded the source code of CouchDB 1.0.1, then ran the usual:
./configure --prefix=/usr/local make sudo make install
- Voila, CouchDB 1.0.1 was installed, the config and database files were still intact, everything worked fine.
Node.js And CouchDB Installation On Ubuntu
Just a quick gist of the script I’ve been using to install NodeJS and CouchDB on several Ubuntu boxes.