Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
Description
As discussed in slack's Docu room on Nov 28 (2018), the key question is:
Is there a way to install just an author instance with CLI? No public. Shorter startup.
Possible (tested) ways:
A) "I always just delete the /magnoliaPublic directory. Works for me."
B)
- mgnl jumpstart
- wait until all is downloaded
- go to the /apache-tomcat/bin dir
- in magnolia_control.sh uncomment or remove the section
# create public webapp(from author webapp) when "installed" file and "magnoiaPublic/WEB-INF" directory doesn't exist - mgnl start
This starts the author
and trying to access the public you'll see:

------------------------
The current behavior is:
- mgnl jumpstart downloads Tomcat and a selected webapp, extracts the webapp to magnoliaAuthor and prepares (creates) also an almost-empty magnoliaPublic folder (with approx 0.5MB of content).
- mgnl start, which is usually the next command issued, copies the content form magnoliaAuthor to magnoliaPublic, installs and starts both instances.
jumpstart command's current switches are:
-v, --version
-p, --path
-m, --magnolia-version
-i, --install-sample-module
-w, --webapp
-s, --snapshot
-h, --help
start command's current switches are:
-v, --version
-p, --path
-d, --dont-ignore-open-files-check
-h, --help
Already with the jumpstart command the user could decide to install and start just a single instance, not both (default, no switch for that). Unfortunately, the -i switch is already occupied to stand for "instance".
(https://documentation.magnolia-cms.com/display/DOCS60/Instances)
I'd suggest then implementing
-d, --deploy-only-one-instance <author|public>
might be suitable for this, e.g.:
mgnl jumpstart -m 5.7 -s -d author
Checklists
Attachments
Issue Links
- mentioned in
-
Page Loading...