I personally provide OSGi bundles.
On Wed, Mar 6, 2013 at 9:12 AM, Fabian Christ <[email protected]>wrote: > Hi, > > I am evaluating the use of Sling for a new project. I have been > studying the documentation of Sling and Jackrabbit for a while now. I > really like the design and the idea behind Sling ;) > > But one thing is still unclear to me: In a normal webapp project, > let's say using PHP, I would organize my source a tree similar to any > other software project and deploy that to a production system. Now, > with Sling and having all the content in a JCR repo things seem to be > a bit different. > > My question is: How does a typical Sling workflow and project layout > look like for a professional application on top of Sling? > > I see the following options: > - Use REST API and develop directly on the content repo > - Configure somehow a file resource provider and organize the sources > and scripts in a local file system > - Implement own OSGI servlets and integrate them with Sling > > What is the way to go? I would assume that the REST API is more for > testing and a quick entry for prototyping but I am more looking for > the development of a real application. > > When everything is inside the content repo, how is the process of > deploying local developments to a remote production environment? What > about version control for the sources? > > Some experience and best practice insights on how to start would be > helpful. > > Thanks, > - Fabian >
