TYPO3 Deployment

Added by Maik Hagenbruch over 6 years ago

TYPO3 Deployment (v6 and beyond) - Tobias Liebig

Many agencies and maintainer of large and/or a lot of TYPO3 installations know: It is hard to implement a fully (or mostly) automated deployment process for TYPO3 (v4/v6) projects in multiple stage setups (e.g. multiple development systems, integration system, live system).
Many people start implementing little helpers and solve some single tasks. But in some cases TYPO3 lacks on some build in support and there is no „best practice“ for several issues.


Replies (6)

RE: TYPO3 Deployment - Added by Philipp Gampe over 6 years ago

Many agencies and maintainer of large and/or a lot of TYPO3 installations know: It is hard to implement a fully (or mostly) automated deployment process for TYPO3 (v4/v6) projects in multiple stage setups (e.g. multiple development systems, integration system, live system).

Many people start implementing little helpers and solve some single tasks. But in some cases TYPO3 lacks on some build in support and there is no „best practice“ for several issues.

An automated deployment includes many different tasks like

releasing code from a CVS (like Git) to a system (development system, integration system, live system)
execute tasks like clearing caches, activate extensions, apply database changes, update TemplaVoila mappings, execute SQL, create or update records, …
migrating database changes from one system to another (like migrate a partial page tree from the integration system to the live system)

I like to work on three main parts to make TYPO3 support automated deployments:

a „best practice“ documentation
  • how to structure the base setup for a project to be „deployment friendly“ (externalize TypoScript/Templates in files, structure TypoScript, structure files and extensions, how to make stuff reusable for multiple projects „default setup“)
  • how to use and structure a CVS like Git for the project (branching, releasing)
  • how to setup and use TYPO3.Surf for deployments
  • how to setup and use a jenkins for deployment/CI (testing, building/packaging)

implement extensions (or even extend in the Core itself) to automate some important tasks for a deployment process

EXT:coreapi to automate tasks during deployment like clearing caches, install/activate extensions; all the important stuff, one normally needs to do „by hand“ in the backend. (already in progress)
EXT:migrations to script complex changes, execute database and „Content“-migrations
review and finish up EXT:identity for UUID support in the core, e.g. for referencing in TypoScript and as basis for a concept and implementation for content-migrations

working on TYPO3.Surf
TYPO3.Surf will be the suggested deployment tool. It needs to get extended by adding v6-specific tasks/application. Also some refactoring of options/settings handling is required.
As TYPO3.Surf is already the deployment tool used by FLOW3 and Phoenix, they will also benefit from this improvements.

I see a huge benefit for agencies, if TYPO3 would support automated deployments. Thus i will try to back most of the working time by sponsoring of several agencies. I'm aiming for 3-4 month of fulltime working on this project.

Further i like to organize at least 2 meetups.

The first one should bring together some representative of agencies, who already work with a self-build deployment process or want/need to setup one. The main idea is to collect the ideas and requirements and see what's really missing to make TYPO3 deployment friendly. In the end we should have a final concept.
The second meeting is planned to get things done, to work on and finish the three main tasks descriped.

Looking at the spreadsheet, this budget is for sprints only ?

RE: TYPO3 Deployment - Added by Patrick Lobacher over 6 years ago

Sounds very reasonable for me - two codesprints and best practice documentation fit good in the budget and the topic itself is needed by everyone who works with more than just a single installation. So +1.

RE: TYPO3 Deployment - Added by Volker Graubaum over 6 years ago

Would say travel cost with 150 € should be fine :-). Otherwise great idea and go for it.

RE: TYPO3 Deployment - Added by Tobias Liebig over 6 years ago

Philipp Gampe wrote:

Looking at the spreadsheet, this budget is for sprints only ?

Yes, the budget is meant to organize and cover the meetups/code sprints.

Most of the actual coding work should/might be backed by volunteer and sponsored (by agencies, which i need to find) work. Actually i'm thinking of a startnext project like Joey did to cover my expected working time of 3-4 month.

RE: TYPO3 Deployment - Added by Tobias Liebig over 6 years ago

Volker Graubaum wrote:

Would say travel cost with 150 € should be fine

I'm fine to cut that down to 150€ :-)

RE: TYPO3 Deployment - Added by Andreas Otto † over 6 years ago

Volker Graubaum wrote:

Would say travel cost with 150 € should be fine :-). Otherwise great idea and go for it.

Yes, a great idea which should be supported.

    (1-6/6)