I was working off of the comments in the local.ini, which suggest using
{couch_httpd, start_link, [https]}
But your explanation makes it obvious. Thanks.
On Thu, Oct 13, 2016 at 4:00 PM Robert Samuel Newson
wrote:
> A common mistake is to use couch_httpd instead of chttpd
A common mistake is to use couch_httpd instead of chttpd when configuring the
httpsd daemon.
This;
{couch_httpd, start_link, [https]}
will configure a new SSL-enabled listener equivalent to :5986, the node-local
port. This port should not bound to anything but 127.0.0.1, so SSL-enabling it
In my last post you told me (and the docs have always been clear in this
regard) to use port 5984 on my single node, 2.0.0 build.
If I use Fauxton to complete the single-node setup it asks for "Port that
the Node uses" and defaults to 5984. So far this is all fine.
I'm using ssl nearly
Ugh, that on is on me, sorry!
Best
Jan
--
> On 13 Oct 2016, at 19:43, Timothy McKernan wrote:
>
> The setup endpoint was easy to use and I have a lot more confidence that
> I've set it up correctly, thanks.
>
> The only thing that threw me was the endpoint name and
The setup endpoint was easy to use and I have a lot more confidence that
I've set it up correctly, thanks.
The only thing that threw me was the endpoint name and json format are
incorrect in the README. I was going to fork and fix it but it looks like
Hello there!
The CouchDB weekly news is now live at:
https://blog.couchdb.org/2016/10/13/couchdb-weekly-news-october-13-2016/
Highlights include several news posts on CouchDB 2.0, a PouchDB use case, plus
a little something on LaCroix.
You can help us spread the news by sharing
> On 12 Oct 2016, at 22:40, Timothy McKernan wrote:
>
> You are right, I did skip over it. I apologize for the easy miss.
>
> If you'll bear with me, here is what I was seeing, and why I skipped over
> it: I only use ssl and was trying to automate that step (for an