[NPMCLI-240] Create 'content-importer' directory and point to it Created: 25/Jun/20  Updated: 20/Jul/20  Resolved: 25/Jun/20

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes

 Description   

As a developer I want to easily import content at install of Magnolia and throughout the projects life, so I can start with content and configuration.

The CLI jumpstart command creates a 'light-modules' directory, and changes the magnolia.properties configurationn to point to it.

The command should also create a 'content-importer' directory adjacent to it (if one does not already exist) and it should change the magnolia.properties file to point to it.
`magnolia.content.bootstrap.dir`

It should also configure the automatic import at install:
`magnolia.content.bootstrap.initial=true`



 Comments   
Comment by Christopher Zimmermann [ 25/Jun/20 ]

Duplicates: https://jira.magnolia-cms.com/browse/NPMCLI-238

Generated at Mon Feb 12 04:47:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.