[DOCU-111] Controlled software development lifecycle (SDLC) Created: 21/Jan/11  Updated: 30/Jan/15  Resolved: 30/Jan/15

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

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Antti Hietala
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File dev-and-deployment-diagram.jpg    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Document best practices for a controlled software development lifecycle (SDLC). This question is asked on the user list by organizations that have middle to large deployments and need to control deployments. We could turn the writeup into a Tech Brief.

  • What is meant by controlled SDLC and what are its benefits?
  • How to set up segregated development, test and production environments?
  • How to deploy templates and code from one environment to the next? (answer: modules, version handler, install tasks)
  • Using a single WAR file with multiple configurations
  • How to deploy content from one environment to the next? XML export, Packager module, activation.
  • How to set up security so that developers don't have access to the production environment? Important in financial organizations that have IT compliance requirements. How to demonstrate the security setup to auditors?
  • Best practices for Magnolia upgrade process and disaster recovery. See architecture diagrams
  • Focus on setup, how to do updates.
  • Check with Christian/Philipp on dev, staging, production setup. Was something written earlier?


 Comments   
Comment by Christian Hauser [ 10/Apr/12 ]

As a first step it would be helpful to have an overview of development best practices and processes including above illustration here:
http://documentation.magnolia-cms.com/developing.html

See also text on STK/ETK and best practices here in 'Why Magnolia CMS Enterprise Editions? (en,de)':
https://docs.google.com/document/d/1qM4OZm4nky52PZ0MkUiNOrr4O5yF7v0kziBbw2tMUQE/edit

"The Magnolia CMS development best practices for Templating Kit is more than a bunch of templates or MVC (Modell, View, Controller) layout, it’s an overall recommended best practice in the development (Eclipse, Maven), staging and distribution of the underlying technical elements of a web site (Java Application Servers). "

It's difficult to underline above statement with some links providing an overview of 'this' best practice.

Comment by Christian Hauser [ 11/Apr/12 ]

A sample I wrote today in a RFP:.

Q: State of the Art Entwicklung

Das zum Einsatz kommende CMS verfügt über eine leistungsfähige Entwicklungsumgebung für die Realisierung von Erweiterungen. Die Unterstützung von State of the Art Entwick-lungswerkzeugen muss gewährleistet sein. Die Entwicklung muss Code-Hervorhebung, Code-Vervollständigung und Debugging Funktionen aufweisen.

A: State of the Art Entwicklung unter Java Standards mit

  1. Entwicklung unter MVC in Eclipse mit lokaler on-the-fly Kompilierung für die Entwickler, Anbindung an SVN/GIT unter Maven
  2. Überführung der JAR/WAR mit Maven auf ein Test System mt Java Applikation Server
  3. Überführung der JAR/WAR mit Maven auf ein Autor und Pub-lik System mit Java Applikation Server
Generated at Mon Feb 12 01:06:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.