> On 5. Jul 2018, at 11:32, ermouth <ermo...@gmail.com> wrote:
>
>> convenience of one file on disk per database is gone, but is there
> anything else
>
> There were serious issues with single node shards (or whatever those pieces
> were) during upgrade from 2.1.0 to 2.1.1. I read only brief report, but
> remember it completely broken tests in some bizzare way, like inability to
> save docs with particular _id ranges.
This is rather inaccurate. The issue was a change of vm.args -name, that
made existing shards unreadable. A regrettable regression, but only a config
issue, that is a one line change to fix.
There was no technical issue here.
>
>> could you unveil this secret, please?
>
> There’s nothing secret here, theoretically you have to insert two oneliners
> into chttpd_auth and then rebuild. Obvious task for end user )
>
> -export([proxy_authentication_handler/1]).
> and
> proxy_authentication_handler(Req) ->
> couch_httpd_auth:proxy_authentication_handler(Req, chttpd_auth_cache).
>
> But as I can recollect it also finally broke things in some bizzare way.
>
>
> ermouth
>
> 2018-07-05 11:59 GMT+03:00 Johs Ensby <j...@b2w.com>:
>
>>>>
>>>> Proxy authorization which is also in docs, but absent in 2.x.
>>>
>>> it is not absent, just not exposed by default. You can configure to
>> enable it (it’s just not documented ;)
>>
>> Hi Jan,
>> could you unveil this secret, please?
>> johs
>>
>>
>>
>>> On 5 Jul 2018, at 10:53, Jan Lehnardt <j...@apache.org> wrote:
>>>
>>>
>>>
>>>> On 5. Jul 2018, at 10:20, ermouth <ermo...@gmail.com> wrote:
>>>>
>>>> Proxy authorization which is also in docs, but absent in 2.x.
>>>
>>> it is not absent, just not exposed by default. You can configure to
>> enable it (it’s just not documented ;)
>>>
>>>> Single-node install without shards.
>>>
>>> Both the /_setup_cluster endpoint and the Mac binaries already set q=1 &
>> n = 1 on setup. Everyone else can configure it.
>>>
>>> Best
>>> Jan
>>> —
>>>
>>>>
>>>> ermouth
>>>>
>>>> 2018-07-05 10:10 GMT+03:00 Johs Ensby <j...@b2w.com>:
>>>>
>>>>> This thread reach out to CouchDB 1.x users to generate a list of
>>>>> "must-fix" issues that is preventing users to upgrade to the latest
>>>>> version of CouchDB.
>>>>>
>>>>> It is in response to Joan's comment below regarding the
>>>>> non-technical proposal to make a project decision to terminate
>>>>> official Apache support for CouchDB 1.x.
>>>>>
>>>>>> On 5 Jul 2018, at 06:31, Joan Touzet <woh...@apache.org> wrote:
>>>>>>
>>>>>> As for things in 2.x that are "must fix" before people can upgrade, I
>>>>>> too would like to see pull requests for those. Once again, your help
>> is
>>>>>> most welcome in this - both in identifying a definitive list of those
>>>>>> must-fix issues, as well as code towards fixing them. If you'd like
>>>>>> to help with this important work, please start a new thread.
>>>>>
>>>>>
>>>>>
>>>>> Mine is CouchDB as a proxy.
>>>>> The feature described here is not working in 2.1.1
>>>>> http://docs.couchdb.org/en/2.1.1/config/proxying.html?highlight=_proxy
>>>>>
>>>>> Johs
>>>>>
>>>
>>> --
>>> Professional Support for Apache CouchDB:
>>> https://neighbourhood.ie/couchdb-support/
>>>
>>
>> ………………………………………
>> Johannes Ensby
>>
>>
>> Business to Web AS
>> Tollbugata 8, N- 0152 Oslo, Norway
>> +47 611 00 006 (mobile)
>> +47 611 00 700 (switchboard)
>> j...@b2w.com
>> www.linkedin.com/in/ensby
>> www.b2w.com
>>
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
