[DOCU-1052] Update "Setting up a Magnolia bundle" - mentioning magnolia-now-dev-bundle Created: 03/Jul/17  Updated: 13/Apr/18  Resolved: 13/Apr/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Done Votes: 0
Labels: mnow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Update the sections:

  • Magnolia Tomcat bundle
  • Installing the local Magnolia bundle

See inline comments from Nicolas and me.

Instead of ...

Ideally, the Magnolia bundle for local development is bundled with a Tomcat application server containing the same apps and modules as those installed in the cloud-based Magnolia NOW package. Unfortunately such a bundle does not exist yet. 

We could mention:
When developing light module only, a CE bundle is fine.
Otherwise use the info.magnolia.now:magnolia-now-dev-bundle which contains the same modules and content (no demo!) as on a NOW subscription package.
There are 2 little "problems"
(1)

mgnl jumpstart -n

does not exist / work yet, ... but maybe / hopefully soon.
(2)
info.magnolia.now:magnolia-now-dev-bundle currently is in a internal nexus repository
(magnolia.internal.releases)
nbarbe will move the artifacts to the enterprise repos ... then we can provide artifact links to the tomcat-bundle of the NOW-bundle.targz

As soon as (2) is resolved, we can do a first part of an upgrade of this page.



 Comments   
Comment by Christoph Meier [ 13/Apr/18 ]

That's actually done

Generated at Mon Feb 12 01:14:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.