not sure what the changes are here
updated linux install script for ubuntu on ec2 for #838
for #838 #827 #832 now the testing auth server doesnt use a port, and the testing corpus server has CORS proxy to be usable in the new chrome store policy
for #838 #828 #827 centralizing all creation of corpus urls to ensure that if the user has an old dev testing corpus, it will use the new testing corpus server
removing urls in permisions to test the new CORS on the new database servers
so hisakonog can debug the app reverting for now

Revert "removing urls in permisions to test the new CORS on the new database servers"

This reverts commit b9d2372ad8985de95cfece6363411f73515e3ba8.
small tweeks testing why CORS is working for everthing except the _session in couchdb for #838
switching back to no urls in the permissions

Revert "so hisakonog can debug the app reverting for now"

This reverts commit deb67bd3e872ae54765181d9362a2860fbaabc35.
found bug in localhost detection, important for running on touchdb on android and for testing cors proxy for #838
for #838 tested the CORS-proxy project (https://github.com/gr2m/CORS-Proxy)

 customized for a new CorpusWebService (https://github.com/OpenSourceFieldlinguistics/CorpusWebService) which will proxy a local couchdb for us for #838, it appears to work for couchapps, next step is to test it with nginx https wrapper on the testing server to be able to contact it from the chrome app
moved back up user function into the app so that the views aren't required to execute it fixes #842
Some more cases where corpusdev wasint being called because lingsync was more general
small changes for testing #838
for #838 testing for upgrade to 1.38 for creation of new corpora on the new corpusdev server
converted all $.ajax to OPrime.makeCORSRequest to push all requests to be identical to debug which ones work and why for #838
updating and fixing small bugs in the corpus connection information and the transition from ajax to a cors request for #838
attempting to find out if the jquery couch is the source of the lack of CORS success in the chrome app.... for #838
bringing in jquery couch from couchdb v 1.2.1 there are some changes in error handleing and signup, but nothing to help with cors.
added  xhrFields: {withCredentials: true} everywhere in jquery couch

we now have an apparently CORS enabled jquery couch, or at least a rough draft. I can log in, open data, save data in the chrome app while contacting a couchdb wrappd in https://github.com/OpenSourceFieldlinguistics/CorpusWebService the CORS-proxy project customized for couchbd and nginx or another proxy.

also removed the reference to browser.msie

http://bugs.jquery.com/ticket/13214

so we could upgrade to jquery 1.9 fixes #849

http://stackoverflow.com/questions/11728343/set-cookie-session-not-being-set-after-sign-in-with-cross-domain

We were getting cookies fine, it was hard to tell but you can tell by opening another tab and getting into the databse and seeing you're logged as the intended user. The problem was that jquery couch wasnt sending credentials back so the couchdb couldnt tell that we were in the session. When not in a CORS situation the cookie is added but you must explicitly add it if you are in  CORS relationship to the database.

and apparently fixes #838 still more tests to confirm that this doesnt in turn break the couchapp when it runs out of the actual database.
for #838 removing slash from session, it is working without it

nginx seems to be having problems without a slash when contacting couchdb in #843