Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-233

single service deployment

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • 2.1 Final
    • 2.0 Final
    • admininterface, core
    • None
    • It should be possible to deploy multiple magnolia instances under one container service

    Description

      So, what is to do if you want to deploy magnolia as a war without changing server.xml?

      The point is the context of the web application. This means that every URL created by
      Magnolia start must start with the correct context. For example all URL produced by the author instance should start with
      /author and all URL produced by the public instance should start with /public

      First you have to define the context as a prefix in the config section (this should not be a problem)

      Then there are two possibilities:
      1. Setting up a filter which checks the URLs and does respective rewriting (let's call it "link checking"). This would mean that Magnolia must parse every JSP page and do the rewriting. Of course we could check broken links here as well...
      2. Whenever you create a URL make sure to use this prefix (admintemplates and custom templates/paragraphs).

      In either ways the Magnolia team should support one of these.

      Ralf

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              scharles Sameer Charles
              scharles Sameer Charles
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD