Closed mostlygeek closed 11 years ago
Hey @lloyd do you think you can add this to your plate? It'll probably be a lot faster for you to just hack it together than for me to figure out ldapjs and then hack it together. :)
Yessir. How about I hack this support into the existing test server. I need it for meaningful unit tests anyway.
-- lloyd (thumb-typing)
On Apr 23, 2013, at 4:35 PM, Benson Wong notifications@github.com wrote:
Hey @lloyd do you think you can add this to your plate? It'll probably be a lot faster for you to just hack it together than for me to figure out ldapjs and then hack it together. :)
— Reply to this email directly or view it on GitHub.
Yah that's a good idea. The test server fixture and my dirty little ldap daemon can be the same code. For test-server/server.js
it can just import the server and make it listen on a port...
FYI: For my test (vagrant) setup I'm going to make clortho talk to this LDAP server over TCP. Then hack in com.mozilla.localdomain into my /etc/host file (on my laptop) so when I test it in my browser it should go talk to clortho -> ldap correctly. Hmm... now that i type that out I might need a persona enabled site I can also run locally and I can trick w/ my own DNS.
Do we have a persona test site I can easily run in a local vm?
I'm such a hermit, never want to leave localdomain...
Closing this one see #39. It seems that a PR generates an issue so might as well start w/ the PR and then do commits.
Create a very simple ldapjs server in
/test-server/server.js
. These are the requirements:node test-server/server.js
Why: