-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 126, Kromeriz 130, Kromeriz 131, Kromeriz 132
-
8
Jumpstart should support grabbing a magnolia webapp and a tomcat and putting them together in a working setup that functions the same as a bundle.
Reason:
- When starting a real project, a demo project often has to be removed which can be complicated.
- Magnolia provides more useful webapps than it provides bundles.
For example: several of these webapps are more useful for starting actual projects than the bundles because they do not include demo projects.
Info on existing bundles and webapps:
https://documentation.magnolia-cms.com/display/DOCS/Bundles+and+webapps
—
Proposed options:
Propsal 1
Behaviour with no options
mgnl jumpstart Default becomes:
- It prompts you on which edition you want (empty, community, enterprise-edition-standard, enterprise-edition-pro, cloud. Community is the default.)
- If you choose community, ee-std, ee-pro, then It prompts you with or without demo (y/n) n is the default
Additional options
Specify the full webapp or bundle name:
mgnl jumpstart --webapp <webapp name>
mgnl jumpstart --bundle <bundle name>
ie
mgnl jumpstart --webapp magnolia‑enterprise‑standard‑webapp
Proposal 2
Same as above - but
mgnl jumpstart Default becomes:
It prompts you which one you want- from these options:
- cloud
- empty
- community (default)
- community-demo
- enterprise-standard
- enterprise-standard-demo
- enterprise-pro
- enterprise-pro-demo
- is causing
-
NPMCLI-166 webapp chooser does not show all webapps
- Closed
-
NPMCLI-167 update jumpstart to use new cloud webapp GAV
- Closed
- is depended upon by
-
NPMCLI-61 Jumpstart should allow getting bundle without travel demo
- Closed
- is related to
-
MGNLTOMCAT-1 Supply a downloadable magnolia preconfigured tomcat without magnolia itself
- Closed