Dashboard > Magnolia Development > ... > Concepts > Concept Deployment
Concept Deployment Log In View a printable version of the current page.

Added by Philipp Bracher , last edited by Philipp Bracher on May 14, 2008  (view change)
Labels: 
(None)

Deployment

Problem:

  • deploying changes (to jsps, configuration) is complicated
  • many developers do not have write access to the container
  • two solutions for the same thing: modules / packager

Goal:

  • deploy modules without having write access to the server
  • should be able to trigger update/install manually

Ideas:

  • documentation
  • tool for uploading/installing a module jar
  • extracting files from jcr content (jsp in repository)

Issues:

  • clustered instances (extract the files)
  • you can't write to the filesystem in all containers

Resources:

  • concept 2 days
  • implementation 5 days
Powered by a free Atlassian Confluence Open Source Project License granted to Magnolia International. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators