Build should include OpenSocial container
Opened this issue · 4 comments
Code currently prereqs a local copy of Apache Shindig running in same App Server at the root context. We should bundle Shindig (or Rave) into the WAR so that the DevGuide is 'plug and play' for anyone trying to use it.
Are you thinking of a maven project which depends on Shindig or Rave?
Yes. For example, Rave has a maven target that generates a complete tomcat zip. Or maybe we just want something like a Shindig WAR with doc inserted into it. Both would make it really simple for a developer who knows nothing about OpenSocial to get something running immediately.
Should the guide be part of the artifacts that are downloaded or just a separate piece of documentation that lives elsewhere, like on the shindig and / or rave sites? We discussed creating a cookbook for developers to build a container.
I see the guide as being an artifact that you can download AND a hosted piece of documentation that is web accessible. Being able to download it lets you tinker with it. Being able to hit it on the web at anytime makes it convenient.