[
http://jira.magnolia.info/browse/MAGNOLIA-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18477#action_18477
]
Gregory Joseph commented on MAGNOLIA-2170:
------------------------------------------
Having the repository outside has been possible for as far as I've been using
and working with Magnolia, by setting the {{magnolia.repositories.home}} in
{{magnolia.properties}} Indexes are in there too. Cache and tmp directories are
also configurable through {{magnolia.properties}}. With 3.7 you'll have the
possibility to have your (freemarker) templates either (or both) outside the
webapp, (anywhere on the filesystem) or in the repository. I've been working
for a little while with a non-exploded war in jetty and haven't noticed
anything else that needed to write to the filesystem, but if you have a
specific setup in mind and some time on your hands, by all means, please try a
3.7 snapshot (we can upload some for you, but you'll want to build your own war
anyway)
One extra option would be (and it might already be feasible, would have to
check) to be able to specify the location of the {{magnolia.properties}} file
through a jvm/system property. At the moment, the locations where its looked
for are specified in the web.xml and this mechanism is explained here:
http://documentation.magnolia.info/cookbook/using-a-single-war-file-with-multiple-configurations.html
> template directory location should be configurable (and outside the app
> directory)
> ----------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2170
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2170
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.5.8
> Reporter: Dan Greening
> Assignee: Gregory Joseph
> Fix For: 3.7
>
>
> Ideally, it would be possible to make the servlet container read-only,
> storing the repository and template files (and any other writable files)
> outside the app directory. This would allow for "instant upgrades" by just
> dropping in a new WAR file. Today, I think, Magnolia really violates the
> principles of a WAR file, which is that it should be self-contained and not
> writable.
> I attempted to remove all writable/changable files and directories to outside
> the directory, and then marked the app directory read-only to diagnose
> problem areas. In Tomcat, it is possible to configure the
> magnolia.properties file location outside the app directory (and by changing
> that version of magnolia.properties, you can move the repository directory)
> out of the servlet container. However, you cannot relocate template files
> outside the app. In addition, the installation process makes changes to the
> contents of the app directory; kind of annoying.
> Would be used by many, I suspect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
