[NPMCLI-238] 'mgnl jumpstart' command should also create 'content-importer' directory Created: 04/May/20  Updated: 25/Mar/22

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

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

Issue Links:
Relates
relates to MAGNOLIA-7786 Magnolia webapps should have a defaul... Selected
relation
is related to MGNLCI-22 Bootstrapping/importing content with ... Closed
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
Epic Link: Content Importer Obstacles

 Description   

As a developer I want to place import files in a directory outside of the magnolia webapp directory so that I can work in a convenient and consistant way to what I know from the 'light-modules' directory.

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`

 

 


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