Heterogeneous deployment/old
From Wikitech
< Heterogeneous deployment(Difference between revisions)
(add ac ouple plan points :D) |
|||
| Line 20: | Line 20: | ||
Plan: | Plan: | ||
# Replace [[scap]] with [[wmsync]] | # Replace [[scap]] with [[wmsync]] | ||
| + | # devise a way to list which sites get which version | ||
| + | # tweak 'live' (w/) stub scripts to check the above list and divert to appropriate $IP | ||
# ... | # ... | ||
# profit! | # profit! | ||
(ok....we don't have a full blown plan yet, but we know scap needs work) | (ok....we don't have a full blown plan yet, but we know scap needs work) | ||
Revision as of 07:20, 9 February 2011
Project notes for multiple extension/core version deployment.
Requirements
- Multiple core versions
- Multiple extension versions
- Ability to have at least staging + production
Nice to have
- A/B testing
Issues:
- bits: $wgExtensionAssetsPath and $wgStyleSheetPath
- l10n cache
- separate $IP, but shared configuration
- scap pushing multiple versions
- downgrading
- (figure out if there are any other shared caches)
- APC cache size
Plan:
- Replace scap with wmsync
- devise a way to list which sites get which version
- tweak 'live' (w/) stub scripts to check the above list and divert to appropriate $IP
- ...
- profit!
(ok....we don't have a full blown plan yet, but we know scap needs work)
