Drupal + WBR: How Warner Bros. Records uses Drupal

Drupal + WBR
How Warner Bros. Records uses Drupal

Tuesday, February 10, 2009

Who am I?
Shaun Haber
shaun.haber@wbr.com

Lead architect, developer, administrator
for Warner Bros. Records


My short talk
1. Background of Drupal at WBR

2. Environment setup

3. Development workﬂow

4. Site implementation


Warner Music Group


WBR Tech

• In-house Tech team
• “Start-up” mentality
• Fast-paced, hectic, and fun!
• We use Drupal... religiously


100+ Drupal Sites
Since October 2006


Environment Setup
• DNS • Serving external pages
• Apache mod_vhost_alias • Using a CDN
• Directory structure • Cron
• Shared code-base
• Symbolic links
• Monikers


DNS


Apache mod_vhost_alias
Dynamically created virtual hosts


Directory Structure
• Directory of web roots

• Directory of Drupal cores

• Directory of contributed (and custom) modules

• Directory of Drupal sites

• All pieced together by symbolic links!


Web roots directory


Drupal env directory


Drupal cores directory


Drupal sites directory


Drupal sites directory

monikers


Drupal modules directory


CCK module directory


sites/all/modules directory


sites/[moniker]/modules directory


Serving external pages?
★ http://theveronicas.com/foo

★ http://disturbed1.com/foo

• Problem: These should be two separate pages.
How to implement using a shared code-base?

• Solution: Don’t place site-exclusive files in Drupal root.
Instead, place each file in a dedicated location and tell
Apache to check there first.


Use mod_rewrite


Site directory

Virtual Drupal root


Using a CDN
• Use RewriteRules

• Symlink to pickup zone


RewriteRule example


Use a symlink for ﬁles

Read by Akamai’s servers


Cron
• Run cron as a command-line PHP script.

• Input list of sites and run cron for each site.


Environment Setup
Recap
• DNS • Serving external pages
• Apache mod_vhost_alias • Using a CDN
• Directory structure • Cron
• Shared code-base
• Symbolic links
• Monikers


Development Workﬂow
• Subversion repository

• Provisioning a dev site

• Development cycle

• Deploying a site

• Development on a production site

• Database synchronization


Subversion Repository


Provisioning a Dev site
• Name the site (moniker!).

• Create vhost.

• SVN Copy skel site folder.

• Create symlink(s) in drupal sites folder.

• Create database.

• Populate settings.php.

• Run install.php.


Development Cycle
SVN

update
update
update
commit

Local Dev Prod


Remote SVN Update


Deploying a site

• Code

• Database

• Files

• Conﬁgs


Code
• Subversion checkout

checkout
SVN Prod


Database
• Mysqldump + gzip + scp

• Search/Replace dev environment strings

• UPDATE files SET filepath = REPLACE(filepath,
‘mutemath.wbrdev.com’, ‘mutemath’

• UPDATE system SET filename = REPLACE(filename,
‘mutemath.wbrdev.com’, ‘mutemath’

• Create and populate settings.php ﬁle


Files
• Tar + gzip + scp

• RewriteRules for CDN


Conﬁgs
• Change ﬁle paths

• Turn on caching

• Turn off error log to display

• Disable devel and watchdog modules

• Etc.


Development on a Production site

• Code already handled by SVN

• Take snapshot of production DB, copy to dev

• Copy ﬁles over to dev

• Change paths, conﬁgs

• Obfuscate email addresses

• Take note of date and sequences table (D5 only)


Database Synchronization
1. Take dev site down

2. Shift sequenced IDs on Dev

3. Take prod site down

4. Merge content from Prod to Dev

5. QA “new” dev site

6. Copy dev site to prod site

7. Bring “new” prod site live


3
2
1


3 3
2 2
1 1


6
5 5
4 4
3 3
2 2
1 1


11
10

6
5
4
3 3
2 2
1 1


11
10

6 6
5 5
4 4
3 3
2 2
1 1


11
10
6 6
5 5
4 4
3 3
2 2
1 1


11
10
6 6
5 5
4 4
3 3
2a 2a
1 1


Development Workﬂow
Recap
• Subversion repository

• Provisioning a dev site

• Development cycle

• Deploying a site

• Development on a production site

• Database synchronization


Demo


Asyncronous Data
Processing
• Pull model

• Push model


Pull model
• Create a site node type

• Stores db info, document root, URL, 3rd-party API
keys, etc.

• Create acquisition layer

• Aggregate data

• Generate views


01Detail Module Overview

Shaun Haber
Fri Jan 16 2009
Report Filtered View

Chart

Aggregator

Vendor API Bootstrap Query Env Master User
(Service) (XML-RPC) (MySQL) (OS) (API)

Site List


Push model
• Setup site with actions and triggers.

• Setup a message queue system (Spread Toolkit).

• Asynchronously send data via Spread daemon for further
processing.

• XML-RPC callback to the site when data processing
completes.


Questions?
Shaun Haber
shaun.haber@wbr.com

Lead architect, developer, administrator
for Warner Bros. Records


Drupal + WBR: How Warner Bros. Records uses Drupal

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (6)

Ähnlich wie Drupal + WBR: How Warner Bros. Records uses Drupal

Ähnlich wie Drupal + WBR: How Warner Bros. Records uses Drupal (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Drupal + WBR: How Warner Bros. Records uses Drupal

Hinweis der Redaktion