Public instances are installing, configuring and never using several modules. The entire UI itself could be considered redundant in a public instance. Removing all UI elements makes for a lighter and faster webapp. The minimal public instances are easier and faster to scale. They are able to handle publication, REST and web requests. 

Often users will say it's necessary to login to public instances but it's cumbersome to have to login to another instance just to see remote data. That data could easily be viewed from a single UI capable of interfacing with all other nodes in the network. Not limited to the single author paradigm or even one level of deployment.

Git

The minimized light public is found here: https://git.magnolia-cms.com/users/rgange/repos/light-public/commits

Blockers

A minimal public instance for receiving and serving content is really not that far away. Current obstacles:

  • MULTISITE-108 - Getting issue details... STATUS  The multisite module sets a class for DefaultI18NAuthoringSupport. It should be easy enough to break out into another module.
  • MGNLLIC-83 - Getting issue details... STATUS  The Enterprise module creates a message in the license checker command. The would better be handled in the About app module. The command should be relocated. 
  • MGNLSCH-77 - Getting issue details... STATUS  The Scheduler module has seemly un-required ui-framework dependency. It should be removed.

Needed

An author instance should be capable to interface on any node within the network. Assuming this is the desired configuration. The entire network is composed of 3 levels (DEV, UAT, PROD) each containing 3 magnolia instances (1 author, 2 publics). In an environment where the public instance doesn't have a UI then those responsibilities will fallback to the author instances. The author instance should be capable to view data from any of the other 8.

Instance Module

The current situation is a single author instance which typically publishes content to public instances. The configuration for the public instances reside in publishing-core. This needs to be abstracted to an Instance module with an instance registry. The instance itself will define what type and level it resides. The level will act as a "publishing group" for the publishing module. 

Enhanced JCR Browser

The same app but with an additional dropdown(s) for the instance(s). Just being able to view and browse the data is the idea. Editing data in external instances probably is bad practice.

Enhanced JCR Tools

Being able to query external instances and catalog those queries. Even perform a remote export (if possible). 

Enhanced Groovy Module

The ability to activate and execute groovy scripts from author probably would be a useful tool.

Make it possible to configure the groovy console as the public interface without a Vaadin dependency. Essentially make the groovy console the default interface for micro public instances so they can be manipulated directly with command line. Currently the rescue app requires Vaadin. 

  • No labels