Porting changes from debug to production in Typo3

Question

Software Deployment

Gentlemen, has anyone eaten Typo3?

How to organize the deployment of new features affecting new / old modules, changes in templates, themes, several pages so that the collected can be automatically uploaded to the battlefield, and in the event of a sudden akhtung, also automatically rolled back?

Is there such a thing for him at all - or only manually?

Answer 1

New / old modules, as far as I understand, by hand. I have never needed to roll back, but you can always download the old version to disk before updating it (via the admin panel). This is the system level.
Templates (styles, JS / PHP scripts, even TS scripts) - if in the version control system, then back and forth is not a problem. These operations are the domain of site developers (web programmers, layout designers).
Pages - in typo3 there are workspaces, how much they allow you to roll back - I don’t know, but they seem to allow it. And this seems to be the task of a content manager.
This is from a different area of ​​\u200b\u200bthe task, so there is no single control tool.