Using CouchDB to serve HTML.

Question

I'm trying to use CouchDB with HTML/standalone REST architecture. That is, no other app server other than CouchDB and ajax style javascript calling CouchDB.

It looks like cross scripting is a problem. I was using Cloudkit/Tokyo Cabinet before and it seems like the needed callback function was screwing it up in the URL.

Now I'm trying CouchDB and getting the same problem.

Here are my questions:

1) Are these problems because the REST/JSON store like CouchDB or CloudKit is running on a different port from my web page? They're both run locally and called from "localhost".

2) Should I let CouchDB host my page and serve the HTML?

3) How do I do this? The documentation didnt seem so clear...

Thanks, Alex

Answer 1

I can't help thinking you need some layer between the presentation layer (HTML) and the model (CouchDB).

That way you can mediate requests, provide additional facilities and functionality. At the moment you seem to be rendering persisted objects direct to the presentation layer, and you'll have no facility to change or extend the behaviour of your system going forward.

Adopting a model-view-controller architecture will insulate your model from the presentation layer and give you some flexibility going forwards.

(I confess I can't advise on your cross-site-scripting issues)

Answer 2

I think one way is thorugh mod_proxy in Apache. It forward the request from Apache to Couchdb so may solve the cross scripting issue.

# Configuration file for proxy
ProxyVia ON

ProxyPass /couchdb http://<<couchdb host>>:5984/sampleDB
ProxyPassReverse /couchdb http://<<couchdb host>>:5984/sampleDB

Answer 3

There are huge advantages to having CouchDB serve/generate your HTML.

For one thing, the pages (which are HTTP resources) are tied to the data or to the queries on the data and CouchDB knows when to update the etag when the page has changed. This means that if you stick nginx in front of CouchDB and say "cache stuff" you get all the free caching you would normally need to build yourself.

I would push for nginx > apache in front of CouchDB because Apache isn't all that great at handling concurrent connections and nginx + erlang (CouchDB) are great at it.

Also, you can write these views in JavaScript which are documented well in the CouchDB book http://books.couchdb.org/relax/ or in Python using my view server http://github.com/mikeal/couchdb-pythonviews which isn't really documented at all yet but I'll be getting to it soon :)

I hope that view servers in other languages start implementing the new features in the view server protocol as well so that anyone can write standalone apps in CouchDB.

Answer 4

There is a simple answer: store static HTML as attachments to CouchDB documents. That way you can serve the HTML directly from the CouchDB.

There is a command-line tool to help you do this, called CouchApp

The book Mikeal linked to also has a chapter (Managing Design Documents) on how to use CouchApp to do this.

Answer 5

3) you can use CouchDB shows to generate HTML (or any content type)