[Merge] lp:~jderose/ubuntu/trusty/couchdb/1.5.0 into lp:ubuntu/couchdb

[Dave Cottlehuber]

@Jason thanks for the reply,

Re building docs etc, it doesn't really matter, whatever makes sense here. I'm merely pointing out that a large chunk of the dependencies are simply required to build docs, and by using the pre-built tarball that's avoided. Up to you! I do think that python pygments is required for highlighting, but that's not in the list AFAICT.

You're 100% right on the options being a large part of the (re)spwaning issue BTW. This is the right thing to do.

1) per-user instances are already supported, I suspect this will be a matter of documentation and/or config. I've used it for a while, so I suggest you open a JIRA over in CouchDB, we'll nut out what is technically required, fix doc/configs, and you are good to go.

2) only a couchdb admin can modify the local.ini. It stores local admin passwords, the per-instance UUID (used to help replication), and nothing a normal user can modify. This ini file can actually be put anywhere, and the *last* entry in the loaded configuration files is where writable entries need to go. So you can actually put that anywhere you like.

use `couchdb -c` to seee the current config chain:

/usr/local/etc/couchdb/default.ini
/usr/local/etc/couchdb/local.ini

and `couchdb -a /my/config.ini` or `couchdb -A /my/config/dir/` as required.

This is also the answer to (1) above BTW :-)

- install a "normal" couchdb config, don't have the service start up automatically, and then use your own (e.g. upstart's per-user config file http://upstart.ubuntu.com/cookbook/#id97) to set up a per user one, that puts an additional `-a ...` file in there. These settings will over-ride earlier set ones, so you can redirect pidfile, db location, view files, even view servers if you want.
-- 
https://code.launchpad.net/~jderose/ubuntu/trusty/couchdb/1.5.0/+merge/197291
Your team Ubuntu branches is requested to review the proposed merge of lp:~jderose/ubuntu/trusty/couchdb/1.5.0 into lp:ubuntu/couchdb.