Re: 2.0 _users Views

2016-10-18 Thread Robert Samuel Newson
we've begun the process so bear with us. B. > On 18 Oct 2016, at 17:51, max wrote: > > Thanks !! That did the job ! > By the way I need to add some attachments in _users document, I have made a > jira issue as I was asked to do. Do you have any idea when the next version >

RE: CouchDB 2.0 Command Line Options

2016-10-18 Thread Melvin.Lew
Hi Adam, Thanks! I commented out the "-name" in the original vm.args and that worked! Thanks also for the explanation of why it's the case. Is there any chance a command line option will be made available in a future release to specify the node name also? Thanks again. /mel -Original

Re: 2.0 _users Views

2016-10-18 Thread max
Thanks !! That did the job ! By the way I need to add some attachments in _users document, I have made a jira issue as I was asked to do. Do you have any idea when the next version will be released to correct it? 2016-10-18 16:07 GMT+02:00 Robert Samuel Newson : > please

Re: CouchDB 2.0 Command Line Options

2016-10-18 Thread Adam Kocoloski
Hi Melvin, I have a theory here. Did the original $ROOTDIR/etc/vm.args file still contain a “-name” directive? Multiple “-args_file” inclusions are OK, but when there are conflicting “-name” settings the node will default to nonode@nohost. When you specify both “-name” and “-sname” the latter

RE: CouchDB 2.0 Command Line Options

2016-10-18 Thread Melvin.Lew
Hi, I work with Maggie, and had a follow up question about running multiple instances of couchdb using one binaries directory. When setting up a cluster, I understand I need to set the identity of each node in vm.args. I tried the following to have couchdb look in a different location for

Re: 2.0 _users Views

2016-10-18 Thread Robert Samuel Newson
please ensure you have set require_valid_user=true under the [chttpd] section first. To be clear, you want this; [chttpd] require_valid_user=true [couch_httpd_user] require_valid_user=true This covers port 5984 and 5986 respectively. B. > On 18 Oct 2016, at 08:27, max

Re: couchdb upload large attachments

2016-10-18 Thread Joel Wallis Jucá
Hi Tobias. Using CouchDB to store large attachments is not a good idea. You'll end up having issues with replication, etc. A better approach would be storing that file into a proper repository (like AWS' S3) and storing the file metadata into CouchDB. Em 18 de out de 2016 6:09 AM, "Tobias

couchdb upload large attachments

2016-10-18 Thread Tobias Geiser
Hi I try to use couchdb as a software repository for chocolatey. When I try to upload large attachments i get a error that the request was canceled. I've tried to upload the attachment through futon, but also can't upload the large attachment (>2GB). I think this sounds like a timeout problem.