-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
As a new user, I want to have a running magnolia instance as fast and easy as possible, in order to evaluate the product.
current output:
(15:33:44) [robert@tequila-new] ~/magnolia/test $ mgnl jumpstart INFO: Using configuration at /Users/robert/.nvm/versions/node/v6.5.0/lib/node_modules/@magnolia/cli/lib/config/mgnl-cli.json INFO: Using prototypes at /Users/robert/.nvm/versions/node/v6.5.0/lib/node_modules/@magnolia/cli/lib/config/mgnl-cli-prototypes INFO: No path option provided. Will use the default 'light-modules' in the current directory INFO: No magnolia-version option provided. Will use the latest stable version. INFO: '/Users/robert/magnolia/test/light-modules' does not seem to exist. Path will be created automatically. Downloading https://nexus.magnolia-cms.com/service/l...agnolia-community-demo-bundle&c=tomcat-bundle&e=zip&v=LATEST [====================] 100% 0.0s Extracting... magnolia-5.5.1/apache-tomcat-8.5.5/ to /Users/robert/magnolia/test/apache-tomcat Extraction completed Replacing Magnolia properties to prepare it for light development... Changing magnolia.properties at apache-tomcat/webapps/magnoliaAuthor/WEB-INF/config/default as follows: magnolia.develop=true magnolia.update.auto=true magnolia.resources.dir=/Users/robert/magnolia/test/light-modules
Proposal is to add to the bottom:
Magnolia CMS installed. In order to start magnolia, run: ./apache-tomcat/bin/magnolia_control.sh (*nix) apache-tomcat/bin/magnolia_control.bat (Windows)
Acceptance criteria
- is related to
-
NPMCLI-59 Update page prototype to reflect changed name of resources templating functions
- Closed