Hi Hans,
common strategy is to export content of all workspaces in xml and then put it 
in the bootstrap folder of the other instance. upon starting this instance all 
the content will be bootstrapped into repository by Magnolia (as long as the 
repo was empty before startup). In your case if you are reusing the test 
server, you would need to delete its repository prior re-bootstrapping it with 
new data.
Also please keep in mind that if you use jsp for templates (or have any content 
in the mgnl-files folder of your modules) such files will be extracted from the 
jars into file system by Magnolia as well, so during the cleanup you need to 
remove them as well.

HTH,
Jan

On Feb 16, 2011, at 12:47 PM, Hans Wichman wrote:

> Hi list,
>  
> I'm looking for a good way to synchronize 2 repositories that differ in their 
> persistence manager.
>  
> Our scenario is like this:
> - a central test/acceptance server where stuff is deployed for acceptance
> - each developer has his own testserver as a playground on which templates 
> are developed etc.
>  
> Now and then we create a new testserver for new people to play around with 
> without the risk of them breakin things on the acceptance server. We would 
> like them to use the latest data from the acceptance server as starting point 
> though.
>  
> So basically we would like to take the data of the acceptance repository and 
> copy it to their local testserver. The acceptance uses mysql, the local 
> testserver uses derby.
>  
> Does that make any sense? And if so what would be the best way to do that?
>  
> thanks for any thoughts on this.
>  
> Hans
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to