Connecting to Cloudant from Erlang: a quick example of using HTTPS from httpc:request
Wiser heads than me will no doubt already know this but I for one struggled with working out how to do this so I thought I’d put the example up in the hope it will help others. So, what I was trying to do was get and put to a Cloudant database from Erlang. Cloudant requires both HTTPS and a username and password and I struggled to find an Erlang example online.
First, make sure that you can connect to Cloudant over curl and fetch at least the _all_dbs resource. If you can’t, Erlang isn’t going to work either. I found that to get curl working correctly, I needed to update the ca cert bundle that came with it.
Here’s how to retrive _all_dbs for your Cloudant account using curl:
curl https://username:password@username.cloudant.com/_all_dbs
where username is your Cloudant username and password is the password associated with your username. For example, if your username were ‘foo’ and your password ‘bar’, here’s the command you would use:
inets:start(),
ssl:start(),
httpc:request (get, {“https://foo:bar@foo.cloudant.com/_all_dbs”, []}, [{ssl,[{verify,0}]}], []).
It is important to remember to start inets and ssl before attempting to use httpc:request. A put to Cloudant is similar, here’s an example that assumes the existance of a database barfoo and a resource widget on your Cloudant instance and also that you have a suitably initialized variable Update which contains the data which you are writing to the widget resource:
inets:start(),
ssl:start(),
httpc:request (put, {“https://foo:bar@foo.cloudant.com/barfoo/widget”, [], [], Update}, [], []).
And there you have it
Reblogged this on lava kafle kathmandu nepal.
lkafle
June 12, 2012 at 11:58
Re curl & certs, use the -k option to ignore the cert validation chain if you’re lazy.
Dave Cottlehuber (@dch__)
July 11, 2012 at 07:52