I absolutely agree that this would be a huge benefit for other people. Apropos production ready: What happened to our neo4j backend? https://issues.apache.org/jira/browse/SHINDIG-1911 My last information in April 2014 was, that it should become part of the Shindig source. Still the issue is unresolved. As far as I know it's the only production ready database backend Shindig has. Regards René
-----Ursprüngliche Nachricht----- Von: Ryan Baxter [mailto:rbaxte...@apache.org] Gesendet: Dienstag, 16. September 2014 14:08 An: dev@shindig.apache.org Betreff: Implementation Guide I think it has become clear that we should really be providing an implementation guide for those who want to consume Shindig. Those of us that have gone through the pain of implementing Shindig know that there are a lot of gotchas along the way, and it is not entirely obvious which pieces of Shindig are production ready by default and which pieces should be replaced with your own implementations. It would also be good to enumerate which configuration options need to be changed in order to properly secure Shindig (locked domains). What does everyone think? This will need to be a true community wide effort as I am sure everyone has their own tips and tricks. Appreciate any feedback, as well volunteers to help. -Ryan
