Hi Adam, Thanks for replying! I need to point it to another location. We plan to have a few instances of CouchDB for different purposes on our dev servers and would like to use the same binaries to start it up (but pointing to different local.ini files on start up). Without the -a option, I'd have to build CouchDB 2.0 3 times (for example) in order to be able to start up 3 instances of it on a dev server.
Maggie -----Original Message----- From: Adam Kocoloski [mailto:[email protected]] Sent: Thursday, October 06, 2016 11:10 AM To: [email protected] Subject: Re: CouchDB 2.0 Command Line Options Hi Maggie, You’re right, the “-a” switch is ignored in 2.0. That’s a miss on our part. I filed https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_COUCHDB-2D3183&d=DQIFaQ&c=nulvIAQnC0yOOjC0e0NVa8TOcyq9jNhjZ156R-JJU10&r=NRwPGDrZo7L6ztGDn5UDKmqnTC5BQkZuuScVw4Hm9u4&m=CvGFCOSao1pTuD2kwqk7Wzhvz_0qdcdqfL_QjL_7E3o&s=LfHg4gH3qRk1Ve2f26b8_Pnj3TqhGxUo0O_duEaLikg&e= . You can still drop files in the local.d directory and they should take precedence over any files in default.* as well as local.ini. There are other undocumented ways to customize the list of configuration files that are consulted using flags in the vm.args file (and probably using some environment variables as well),, but I wouldn’t really recommend going there. Does the local.d option work for you or do you need to point to another location? Adam > On Oct 5, 2016, at 10:20 AM, [email protected] wrote: > > Hi, > > I'm looking to point to a different local.ini than the one located in the > CouchDB 2.0 etc folder. Is there a way to specify this when starting up > CouchDB or is there another way? Looking at the docs, it seems like we > should still be using the "-a" option but after looking at the startup > scripts in the bin folder there is no code there to accept the "-a" switch > anymore. > > Thanks, > > Maggie
