[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MAGNOLIA-2170 stopped by Gregory Joseph.
> Webapp should be markable as read-only
> --------------------------------------
>
> Key: MAGNOLIA-2170
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2170
> Project: Magnolia
> Issue Type: Improvement
> Components: build, core
> Affects Versions: 3.5.8
> Reporter: Dan Greening
> Assignee: Gregory Joseph
> Fix For: 4.1
>
>
> 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-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
