TYPO3 Site Handling and Proxy-Based Traffic Cutover
0 reputation · 20 Dec 2021, 23:07 UTC
A project requires migrating a small application to a new TYPO3 environment while maintaining zero downtime. The proposed strategy involves using a blue-green deployment where a load balancer or proxy directs traffic between the legacy instance and the new installation.
While the Site Handling module allows for precise domain and base URL mapping to specific root pages, the transition involves two distinct filesystem environments. This creates a challenge regarding the synchronization of cached assets and temporary files during the cutover phase.
If the proxy shifts traffic incrementally, users may encounter inconsistent asset delivery if the cache is not unified or synchronized across both environments.
Technical Constraints
- Requirement for zero-downtime transition.
- Use of separate filesystem environments for legacy and new instances.
- Dependency on the TYPO3 Site Handling module for domain mapping.
How can cached assets be synchronized between two separate TYPO3 installations to prevent broken resources during a phased traffic shift? What is the recommended approach for managing the typo3temp and typo3conf/data directories in this specific integration scenario?
typo3