couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <rnew...@apache.org>
Subject Re: local.d/*.ini are not read by couchdb 2.0 rc2?
Date Sun, 31 Jul 2016 22:11:02 GMT
I filed a ticket for it. It'll work before final 2.0 release. 

Sent from my iPhone

> On 31 Jul 2016, at 22:48, Bian Ying <ybian@me.com> wrote:
> 
> Thanks for your response.
> 
> Can this make into rc3 or rc4? It's important for us to have configurations managed in
local.d.
> 
> - Ying
> 
>> On Aug 1, 2016, at 00:44, Robert Samuel Newson <rnewson@apache.org> wrote:
>> 
>> oooh, you might be right there. Fixable, thanks for catching it!
>> 
>> B.
>> 
>>> On 31 Jul 2016, at 09:39, Bian Ying <ybian@me.com> wrote:
>>> 
>>> I guess developers here may give some insight to me. ;)
>>> 
>>> - Ying
>>> 
>>> Begin forwarded message:
>>> 
>>>> From: Ying Bian <ybian@me.com>
>>>> Date: July 30, 2016 at 23:19:27 GMT+8
>>>> To: user@couchdb.apache.org
>>>> Subject: local.d/*.ini are not read by couchdb 2.0 rc2?
>>>> Reply-To: user@couchdb.apache.org
>>>> 
>>>> Hi,
>>>> 
>>>> I’m using the official docker image of couchdb 2.0 rc2 and want to mount
some local configuration under local.d. 
>>>> Per document (http://docs.couchdb.org/en/1.6.1/config/intro.html) (does it
still apply to 2.0?), it should work. But I
>>>> just don’t make it. This is the command I used to start the container:
>>>> 
>>>> $ docker run -it -v /home/ybian/local.d:/opt/couchdb/etc/local.d -p 5984:5984
klaemo/couchdb:2.0-rc2
>>>> 
>>>> There is one *.ini file under /home/ybian/local.d where I added cors and
admin user configuration. I also verified that
>>>> this directory got mounted successfully by inspecting the container. But
the configuration does not take any effect.
>>>> Seems to me that the *.ini file under local.d was not read at all.
>>>> 
>>>> I also found that `couchdb -c` command mentioned in the doc above does not
work to show configuration file chain 
>>>> anymore.
>>>> 
>>>> Is local.d still expected to work in 2.0?
>>>> 
>>>> -Ying
>> 


Mime
View raw message