Page History

...

See Dave's architecture overview and Harry's instructions on providing your own shindig services for more details.

...

• config/container.js - Declare your list of supported fields for each datatype, configure url templates for proxying, navigation, etc. Configure use of secure tokens.
• common/conf/shindig.properties - http caching and rewriting config.
• Whatever configuration your classes need.
• Enabling Shindig Administration -> Shindig Administration

Deployment

Build a WAR file. Take the one build in the server/pom.xml file of the distribution as an example. Deploy this WAR on an application server running in a different domain from your container. This is important, for security.

...

• Generate tokens for the iframes. (Code examples for this are needed).

• Install rpc_relay.html on your site to allow communication between gadget and container javascript. For example if you have
  shindig running on gadgets.example.com and your container is on www.example.com then you may copy it to http://www.example.com/gadgets/files/container/rpc_relay.html. Then you need to set the path to the new location in your container config file (either config/container.js or your local copy), in this example to the value "/gadgets/files/container/rpc_relay.html". The host name is automatically set in gadgets.js so you probably won't have to explicitly set it (though it doesn't detect https so if your container is on a secure page you'll need to use gadgets.container.setParentUrl() to tell it).