Shindig configuration

[Lucas Anastasiou]

Hi all,

I recently stumbled upon problems to correctly render opensocial
gadgets in edukapp.
This originates from the fact that we are deploying shindig in a
different context (/shindig)
than root (/ ).
To resolve you need to edit a few config files and redeploy war file.
A good resource of how
to do this: http://pillvin.blogspot.co.uk/2008/12/deploying-shindig-in-non-root-context.html
In a nutshell you need to rewrite all urls in default container js
file and correctly configure
the host in shindig.properties

I am about to commit the above instructions in the 'how to build' of
README as well with sample
container.js and shindig.properties files but (I know that is a long
shot) is there a way
to push these changes in an automatic manner while building?

Best
Lucas

[Scott Wilson]

On 24 Jul 2012, at 16:29, Lucas Anastasiou wrote:

Hi all,

I recently stumbled upon problems to correctly render opensocial
gadgets in edukapp.
This originates from the fact that we are deploying shindig in a
different context (/shindig)
than root (/ ).
To resolve you need to edit a few config files and redeploy war file.
A good resource of how
to do this: http://pillvin.blogspot.co.uk/2008/12/deploying-shindig-in-non-root-context.html
In a nutshell you need to rewrite all urls in default container js
file and correctly configure
the host in shindig.properties

Yes, its a pain trying to deploy Shindig anywhere but ROOT as there are a lot of hardcoded paths. It may be easier to deploy the actual store at /store with Shindig in ROOT, and set up an automatic redirect from / to /store.

I am about to commit the above instructions in the 'how to build' of
README as well with sample
container.js and shindig.properties files but (I know that is a long
shot) is there a way
to push these changes in an automatic manner while building?

You can certainly modify config files in deployment using Cargo, e.g. in pom.xml:

            <plugin>

                <groupId>org.codehaus.cargo</groupId>

                <artifactId>cargo-maven2-plugin</artifactId>

                <version>${cargo.version}</version>

                <configuration>

                    <wait>true</wait>

                    <configuration>

                        <configfiles>

                            <configfile>

                                <file>${project.basedir}/../rave-portal-resources/src/main/dist/conf/tomcat-users.xml</file>

                                <todir>conf/</todir>

                                <tofile>tomcat-users.xml</tofile>

                            </configfile>

                        </configfiles>

Best
Lucas