Light Module Deployment

Date

05 Dec 2018

Attendees

• Thomasz, Magnolia

• Vivian, Lemonize
• Philipp, Formica
• Jonas, Formica
• Christian, menzel.com
• Thomas, CIC
• Chris, ... London
• Daniel, UNYMIRA
• Frank, Aperto
• Markus, Arvato
• Arne, Neoskop
• Richard, 
• Anrd, UNYMIRA
• Sebastian Golaszewski, Sympany Services AG 

Light Module Packaging

• Git branch, no packaging
  •  compiled CSS needs to be checked in
  •  alternatively build infrastructure on target machine
  •  no dependency on other tools / systems
  • Git Tags
• Docker images
  • uploading to Kubernetes
• npmjs.org / mgnl cli
  • Magnolia preferred
  • packaging was not meant to be deployed
  • used for FE builds frequently
  • fast builds
• Maven build
  •  slow
  •  complex
• Build on CI / CD infrastructure

Light Module Deployment

• mgnl cli
• Git Client on Remote Machines
  
  • build stack on remote machines vs. checkout final built result
  •  switch branches; production env checks out 
• Tip: ensure author and public use same resources

Pros/Cons

•  quick deployments
•  very quick build times compared to Java / Maven
•  UI

Consents

• Version packages
• Separate FE from BE
  • different deployment cycles
  • avoid Tomcat restarts
• npm vs. Git
• UI is advantageous