Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
HTML Wrap
alignright
classmenu

Related topics:

Magnolia is distributed as two web-applications: author and public. Editors work on the author instance, typically in a secure location inaccessible from the Internet. Editors publish content from the author instance to public instances. Public instances serve the content to visitors. In a typical production setup you have at least two public instances, often more.

...

ConfigurationAuthorPublic
/server/admintruefalse
/modules/ui-admincentral/virtualURIMapping/default/toURINot set.Set.
anonymous roleHas author instance permissionsHas public instance permissions
anonymous system userHas author instance rolesHas public instance roles
SubscribersHas active subscribersHas no subscribers

...

What kind of instance do I have?

...

Each public instance can serve content targeted for a specific geographical to a particular audience or geographic area. For example, one instance serves can serve visitors from Europe and another visitors from the U.S.

...

  • Public instance failure. You have two public instances and due to hardware failure one of them is out of operation for a few days. Start a new public instance to replace the broken one.
  • Sudden high load, also known as Slashdot effect. Start new public instances until the traffic subsides.
  • Public instance blackout. All public instances are corrupted, broken or compromised. No instances exist to serve content.

...

Magnolia instance configurations start from a standard 3-instance setup and scale up. You can add any number of instances for load balancing and high availability. Public instances can subscribe to specific content such as intranet or extranet.