(Re-)Extracting the files of all Magnolia Modules on start up

[Niclas.Meier]

Hi,

We are using Magnolia for quite a while now and got a small deployment issue right now.

The situation is, that we are delivering a packed web application containing the Magnolia CMS and all  required modules. The war will be installed on our platform automatically by “deleting” the previous deployed web app and (re-)deploying the new one.  This process woks quite well, it also makes sure that various unwanted artefacts are removed.
But one problem occurred lately: The the extracted (template) files are deleted also. For the modules that contains our website it’s a minor inconvenience because when we deploy the version number changes and a re-extraction of the module files is forced by a task. But Magnolia and third party modules are a bit tricky. That’s why I am looking for a possibility to enforce Magnolia to extract all Module files on start up.

I hope you have some good ideas ;-)

Best regards
Niclas


--
Niclas Meier

Head of Client Development
IT Development

                                                                                               

scoyo GmbH | Stresemannstr. 163 | 22769 Hamburg | Germany
Phone: [phone] | Fax: [phone]
niclas.meier@...


Sitz Hamburg | Amtsgericht Hamburg HRB 100969
Geschäftsführer: Dr. Ralf Schremper

www.scoyo.de  | http://blog.scoyo.de/

Follow scoyo on twitter: http://twitter.com/scoyo

---

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

[Jan Haderka-2]

first to come to my mind:
- use Freemarker templates and serve them from the repository
- add re-extraction to the startup tasks of your module version handler
or to the start method of your module itself.

HTH,
Jan

On Fri, 2009-10-16 at 09:37 +0200, Niclas.Meier@... wrote:

> Hi,
>
> We are using Magnolia for quite a while now and got a small deployment
> issue right now.
>
> The situation is, that we are delivering a packed web application
> containing the Magnolia CMS and all  required modules. The war will be
> installed on our platform automatically by “deleting” the previous
> deployed web app and (re-)deploying the new one.  This process woks
> quite well, it also makes sure that various unwanted artefacts are
> removed.
> But one problem occurred lately: The the extracted (template) files
> are deleted also. For the modules that contains our website it’s a
> minor inconvenience because when we deploy the version number changes
> and a re-extraction of the module files is forced by a task. But
> Magnolia and third party modules are a bit tricky. That’s why I am
> looking for a possibility to enforce Magnolia to extract all Module
> files on start up.
>
> I hope you have some good ideas ;-)
>
> Best regards
> Niclas
>
>
> --
> Niclas Meier
>
> Head of Client Development
> IT Development
>
>                                                                                                
>
> scoyo GmbH | Stresemannstr. 163 | 22769 Hamburg | Germany
> Phone: [phone] | Fax: [phone]
> niclas.meier@...
>
>
> Sitz Hamburg | Amtsgericht Hamburg HRB 100969
> Geschäftsführer: Dr. Ralf Schremper
>
> www.scoyo.de  | http://blog.scoyo.de/
>
> Follow scoyo on twitter: http://twitter.com/scoyo
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

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