[NPMCLI-195] Add a switch to install and start only a specific instance Created: 28/Nov/18 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Date of First Response: |
| Description |
|
As discussed in slack's Docu room on Nov 28 (2018), the key question is:
Possible (tested) ways: A) "I always just delete the /magnoliaPublic directory. Works for me." B)
This starts the author
------------------------ The current behavior is:
jumpstart command's current switches are: -v, --version start command's current switches are: -v, --version 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 |
| Comments |
| Comment by Christopher Zimmermann [ 28/Nov/18 ] |
|
Problem and use case is accepted. However the name and behaviour of switches must still be decided upon. |