Page History

...

...

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.

...

Author and public instances run identical software. They both have an AdminCentral that you can log into. The differences are configuration and security only.

See also: Changing author to public instance.

What kind of instance do I have?

...

• In AdminCentral, go Tools > About Magnolia.
• Check the /server/admin property in configuration. It is true for author and false for public instance.
• In Java code, use the isAdmin() method provided by the 

  Javadoc
  0 info.magnolia.cms.beans.config.ServerConfiguration className info.magnolia.cms.beans.config.ServerConfiguration renderType asynchronous

   class.
• In a Freemarker template, use the cmsfn.isAuthorInstance() or cmsfn.isPublicInstance() templating functions.

...

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.