[
https://issues.apache.org/jira/browse/SLING-8913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-8913:
----------------------------
Summary: Create Read-Only Sling CMS Instance Type (was: Create Read-Only
Instance Types)
> Create Read-Only Sling CMS Instance Type
> ----------------------------------------
>
> Key: SLING-8913
> URL: https://issues.apache.org/jira/browse/SLING-8913
> Project: Sling
> Issue Type: Improvement
> Components: App CMS
> Reporter: Dan Klco
> Priority: Major
> Labels: backlog
>
> Currently, there is only a single build of Sling CMS which is easier, but the
> build also contains dependencies and code which would not be required in a
> read-only instance. The idea here would be to:
> * separate out the authoring-specific features from the base CMS features
> * remove all non-required dependencies (e.g. Tika Bundle, etc)
> * potentially tweak the configuration for security
> * implement a second builder
> The goal is to build a smaller distribution specifically for creating
> read-only instances.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
