Currently the deployment process consists of 2 steps, that are executed one after another on each deployment:
- svn update
- upgrade database + import language pack (both done for each module)
- resetting various caches + discovering changes in theme files (happens once)
That scheme works pretty fine, when deployment happens on one machine only. When there are several Web Servers in application layer (all using same database) and deployment needs to be made on each of them, then we need to do this instead:
- On master machine:
- svn update
- upgrade database + import language pack (both done for each module)
- On each machine (except master):
- svn update
- On master machine:
- resetting various caches + discovering changes in theme files (happens once)
To make this possible the adm:OnDeploy event needs to be thought to run deployment on step-basis (you tell which steps to run, when needed).