Matteo Pelucco wrote:
> Simple question...
>
> I'm working on a project with several people and we want to share daily
> changes. We work in a local installation of Magnolia 3.6.3
>
> Code changes is shared with SVN, no problem here..
> But how can we share data module configuration without database
> replication?
> And also website entries..
>
> Is it correct (it is a good idea..) to export data module config as XML
> and put them on a "common" module into mgnl-bootstrap folder?
>
> I see also the "sample" module; it has 2 folders:
>
> resources/mgnl-bootstrap/samples
> - config.modules.samples.[...].xml
> - config.modules.samples.[...].xml
> - config.modules.samples.[...].xml
>
> AND
>
> resources/mgnl-bootstrap-sample/samples
> - usergroups.developers.xml
> - ...
> - users.admin.david.xml
> - ...
> - website.mailform.xml
> - ...
>
> I don't know exatcly how bootstrap files are used, sorry...
Database replication won't work. You can't have more than one Jackrabbit
accessing a single database.
To share your configuration you have to export it as XML and the other
developers have to import it.
Bootstrap files are loaded when bootstrapping (when the database is empty).
You have to put the bootstrap files in:
resources/mgnl-bootstrap/${your.module.name}
or
resources/mgnl-bootstrap-samples/${your.module.name}
if you want to have them bootstrapped only in samples mode.
When that database is not empty and you still want configuration to be
loaded automatically you'll have to write a version handler.
Bootstrapping data requires a bit more work:
http://jira.magnolia.info/browse/MGNLDATA-20
Cheers
Philippe
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
