Running locally is what we had currently been doing for testing. However, we felt the need to be able to test on our actual server since the configuration (SSL, etc.) and performance are quite different there than on my local machine.
I think the best option will be Dave's suggestion to install a second instance with a modified ./configure. A second DB on the same instance may also work but the challenge is that we are creating new databases frequently, and our CouchApp has a page for users to select which database to load data from but we don't want databases we create while testing to show up there. There are ways to exclude those databases from the list, but I thought it might be cleaner to have all test data and code in a separate space. I think I'll look into the ./configure options and see how much code I'd need to change to run everything in "dev" mode on a second instance. Duplicating the server is not an option unfortunately. Thanks for your input everyone. -Heather ________________________________________ From: Robert Newson [[email protected]] Sent: Wednesday, April 18, 2012 12:50 PM To: [email protected] Subject: Re: Running a dev instance of Couch Why not run locally? I always 'make dev && ./utils/run' on my machine. B. On 18 April 2012 17:33, Mark Hahn <[email protected]> wrote: > I recommend that you duplicate the server. On amazon that takes only > minutes. Then release is a simple rcp command. > > This is the simplest and safest solution.
