Closed timbertson closed 12 years ago
After getting the .js sources manually and trying it out, I get a 500 when I try to POST my assertion as well. So it's not just a matter of serving up files, the plugin in general seems to be responding with 500 errors. Which is unsurprising, given that serving files is probably not the hard part ;)
I believe this is an issue with activating the plugin. Erlang cannot find couch_httpd_browserid.beam
so it can't run the handler code for the HTTP requests to /_browserid.
Try something like
export ERL_ZFLAGS="-pz /path/to/couchdb/lib/couchdb/plugins/browserid_couchdb/ebin"
before you run couch. How'd it go?
That works perfectly, thanks. Was it an instruction I missed, or should this have been set up by build-couchdb?
I am just running "~/dev/web/couchdb/build-couchdb/build/bin/couchdb" directly, not cd
ing anywhere in particular or sourcing env.sh
. I thought that was fine according to the instructions, but I may have missed something.
Unfortunately, this is getting into intermediate/advanced Erlang and CouchDB development. (Well, it's no more advanced than $RUBYPATH, or $PYTHON_PATH, but those languages are more widely known.)
Some planning is underway about making a proper plugin framework for projects like this, but until then it's a bit of bubble gum and duct tape.
Could this 'workaround' be added tot the documentation? I've spend a long time searching for this solution.
:+1: for getting this info out there; just spent 30 minutes on it
+1 for getting this in the README. Not even google is finding this discussion.
Using a fresh couchdb-build on ubuntu 11.10 with only this plugin enabled (and enabled in config), I can't get http://localhost:5985/_browserid/include.js
When I try, the console gives me:
I've not dealt with erlang stack traces before, but I'm not sure if there's much there to go on...