Hi, On Thu, Jan 30, 2014 at 8:59 PM, Buzzterrier <[email protected]> wrote: >... I was looking to migrate our staging version of Sling to production. I > thought I could just zip up the sling directory and move it to the new > server...
That should work in theory, but I don't think the OSGi state that's stored under sling/felix is tested to be portable between platforms. I'd be cautious unless you are copying between "identical" environments. The alternative is to start with a clean instance and add your bundles to it (maybe from the filesystem using the Sling installer) so that the same state is recreated, using initial content in bundles, that can include configurations picked up by the Sling installer. You also need a way to recreate your system in case of a catastrophic failure, so having this process in place can be useful. And you'll probably need such a process when upgrading to a later version of Sling as well. > ...When I start sling all of our content is missing... It looks like you are using Jackrabbit with a MySQL backend, in which case you'll need to involve Jackrabbit tools to do the copy, or to reset things if copying yourself outside of Jackrabbit. I suspect you need to recreate all Jackrabbit indexes after copying, but I'm not familiar with that setup. You might want to ask on the Jackrabbit users list. -Bertrand
