We are getting to the point where we're going to start getting ready for a sling deployment.
In preparation for that, I'm trying to understand the best process for doing a live deployment. In the pre-packaged war file, jackrabbit and sling come paired together. It would seem in a production environment, you would want to deploy them separately. Is that a correct assumption? How do you configure Sling to point to an external instance of Jackrabbit? I know this is a Sling user list, but the repository initially is bundled with Sling, so I'm going to ask about this, if the answer is see the jackrabbit docs, I'll be happy to go there, but I know they are going to uneducated about Sling. Given that, I'm starting here. Jackrabbit as deployed here seems to store it's documents in a portion of the file system that is under the control of the Application server. Is that a good idea? Shouldn't they be stored somewhere else on the file system? I believe the default system uses Darby, how hard is it to swap out Darby for a real database? Is that necessary? What factors influence that choice? Tony Giaccone
