> > Note: I use MySQL as my repository. If I need to make changes on the source 
> > code I have to build the author instance again, will this override my 
> > modifications to the styles and template definitions I modified in the 
> > previous war file?
> 
> Any configuration stored in MySQL will be persisted, unless an update 
> overwrites this data. We use local instances of Magnolia during development 
> and export our repository modifications to XML and commit these XML files in 
> our build, so they get bootstrapped when the code is deployed.
> I have a problem here. When tables are created in the first deployment of the 
> WAR file they are all created with MyIsam with engine type and I've read in 
> the documentation that this engine type isn't supported. So I need to have 
> ndbcluster as engine type since I'm using a clustered MySQL database. 
>  
The type of engine used at installation is the default type of the given mysql 
instance. If you reconfigure mysql to use ndbcluster by default then this is 
the type that will be used at creation of the tables.
>  
> > And What about the public instance!? is it enough to keep working on the 
> > folder I've extracted from the Apache bundle? or I can create a copy of the 
> > generated WAR file from source code and rename it as public instance?
> 
> You can use a WAR file with multiple configurations: 
> http://documentation.magnolia-cms.com/cookbook/using-a-single-war-file-with-multiple-configurations.html
> I would like to have a separate WAR for my public instance since I will 
> deploy it on a separate server. Can I use the same author instance WAR file 
> and just rename it and change the persistence storage related tags!

Yes, you can have just one war file with different configurations all stored 
inside under WEB-INF/config ... if the subdirectory name there matches the name 
of the warfile the config files in the subdirectory will be merged with the one 
under WEB-INF/config/default 

> I need to know the correct way for the build process and deployment. Whenever 
> I read online I find different topics and each mentioning in a different way. 
> My main question here, if there is a WAR file changes. And I already have my 
> instance setup and there is a folder already extracted from old WAR. how to 
> merge the new changes in the new WAR? If I delete the instance's folder the 
> deployment fails and only succeeds when I drop and recreate the database 
> again!! 
>  

In magnolia.properties (WEB-INF/config/<instance_name> file you can specify 
location for all the data that the instance will persist. By default everything 
is persisted within the folder created for the webapp. However you are free to 
modify magnolia.properties file and move all those data outside of webapp. If 
you do so you can just simply replace old war file with the new one and none of 
your existing data will be affected.

HTH,
Jan

> Nils.
> ------------------------------------------------------------------------
>  VPRO   www.vpro.nl
> ------------------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> 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