Versions Compared

Old Version 1

changes.mady.by.user Julie Legendre

Saved on

compared with

New Version 2

changes.mady.by.user Julie Legendre

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: draft in progress

 

  • Partner sets up maven project reactor as per instructions in readme
  • Specific tricks for cloud are covered in the readme
  • Mention that they have to log in to access the readme - otherwise contact helpdesk
  • Uploading the custom bundles can be 1/yr or 50/week depending on projects. Repeat task.
  • First upgrade from standard bundle to a custom bundle is effort intensive on mgnl side due to dependency/compatibility issues. Only if data must be kept. Simpler alternative is to remove and replce when data doesn't need to be kept.
  • Change in bundle name triggers same effort. +++Warning to not change name unless absolutely necessary.
  • Partner bundle upgrade to newer partner bundle is fine.
  • Mention: light dev can be done in parallel with java/light dev in custom bundles since the light dev is stored in git and can easily be reinstalled.




For customers deploying custom bundles to Magnolia Cloud certain criteria and best practices have to be adopted.

...