Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of tjw@omnigroup.com designates
 198.151.161.1 as permitted sender)
From: Timothy Wood <tjw@omnigroup.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: PUT/POST to app using rewrites+vhost?
Date: Sun, 21 Nov 2010 18:06:16 -0800
Message-Id: <DB92A2C9-E9A8-4E40-91ED-E9D99F9AC8B2@omnigroup.com>
To: user@couchdb.apache.org
Mime-Version: 1.0 (Apple Message framework v1082)


  I have rewrites and vhost support working now (thanks for the help!). =
The next issue I=92m flailing on is how to best perform edits to my =
database, while still using the nice URL structure.

  With a vhost going to /db/_design/app/_rewrite, all the incoming URLs =
get written to have /db/_design/app as a prefix. So, to PUT/POST =
new/updated documents, I added rewrites of:

	{
		"from": "/*",
		"to": "../../*",
		"method": "PUT"
	},
	{
		"from": "/*",
		"to": "../../*",
		"method": "POST"
	},

  I also played a bit with rewriting to a _update/put function. I never =
got this approach working fully before thinking I should just redirect =
up with ../.. in the rewrite. It seems harder to use _update than just =
escape the _design/app namespace this way.

  My question then, is -- is this standard procedure, or should I avoid =
this approach for some reason?

  Thanks!

-tim