1. Archiving in eZ Publish
What to do with all your content
Peter Keung
http://www.mugo.ca

2. Site architecture:
eZ DFS behind a CDN
Akamai
Web Web Web Editor
NFS MySQL MySQL
http://www.mugo.ca

3. Why archive?
Performance and cost
Signs:
ezcontentobject_attribute table: how many million?
ezdfsfile
MySQL master-slave replication delays
Growing cache size: disk performance and size
Distribute traffic to more machines
Different caching needs for archived content
http://www.mugo.ca

4. Delay archiving
Optimize your site
Prune old versions
Prune and combine attributes
http://www.mugo.ca

5. Requirements
Keep same URL
Relate archive and live content to each other
Sometimes edit old content
http://www.mugo.ca

6. Options
Solr
Create static HTML archive
eZ Publish 5
Another eZ Publish install
http://www.mugo.ca

7. More eZ Publish!
Custom object relation(s) attribute
Online Editor links to full URLs
Apache redirect proxy rules
Having date-based URLs helps
RewriteCond %{HTTP_HOST} origin(|m).csmonitor.com
RewriteRule ^(/[0-9]{4}/.*)$ http://stagearchives.csmonitor.com$1 [P,L]
http://www.mugo.ca

8. More eZ Publish!!!!!!
Caching headers on archive install
Use Solr to display unified search and archive
results on topic pages
Ajax or ESI driven widgets in sidebars
Rename var folder
http://www.mugo.ca

9. More eZ Publish!!!!!!
Caching headers on archive install
Use Solr to display unified search and archive
results on topic pages
Ajax or ESI driven widgets in sidebars
Rename var folder
http://www.mugo.ca

10. Implementation steps
Add a new “Archive” object state to mark
articles to be moved
Migrate and purge content
Update existing object relations and Online
Editor links
Re-index content
Apache proxy redirect regular expressions
http://www.mugo.ca

11. More challenges
Maintaining two code bases (small differences)
Maintaining two installs
Subsequent migrations: more precise
http://www.mugo.ca

12. Execute!
Fingers crossed...
Questions? hi@mugo.ca
http://www.mugo.ca