I don't know of any documentation specifically around the configuration files or deploying to a non-root context -- hopefully someone else will chime in if they do.
We did this (deploying to a non-root context) with our shindig installation and it was just a matter of finding all the right places in the configuration files to update the paths. I believe changes were required to both shindig.properties and container.js (and there were multiple properties to change in each file -- I see 15 occurrences of our non-root path in our modified container.js file). There was talk of a patch to make deploying to a non-root path easier -- I'm not sure whether that's been contributed yet though: http://markmail.org/message/dlscm66vvijn3lvd >-----Original Message----- >From: David A. Jafari [mailto:[email protected]] >Sent: Monday, April 04, 2011 5:41 PM >To: [email protected] >Subject: Configuration Documentation > >Hey guys, I'm playing around with Shindig to see if it makes sense to >integrate with my co's enterprise app. I've been trying to reconfigure >the root paths to take into account the content root of our web-app, but >the configuration options for doing so do not seem to be used. I found a >sample shindig.properties file from >http://svn.apache.org/repos/asf/shindig/trunk/java/common/conf/ and >thought the shindig.content-rewrite.concat-url property was what I was >looking for. Modifying this value had no effect and after looking >through the shindig-2.0.0 source code, I don't think it is even being >used. So I have two questions: > > >1) Where might I find documentation related to the configuration >properties for Shindig, if any? > >2) Specifically, which property could I use to rewrite urls such >that they respect a non-root context? > >Thanks, >Dave Jafari
