| Speakers | |
|---|---|
|
Roel de Meester |
| Schedule | |
| Day | Sunday |
| Room | H.1302 |
| Start time | 14:00 |
| End time | 14:45 |
| Duration | 00:45 |
| Info | |
| Event type | Podium |
| Track | Drupal |
| Language | English |
Roel explains how he manages deployments of very large Drupal sites from staging to live servers.
The problem: A client has a live site with 1000's of pages, 10's of blocks containing rather static information. There is almost no user interaction except for a few webforms to collect some user information (contact, request for documentation, etc..)
While the site is live, the client wish to prepare for the next iteration of the website. The new version will contain altered, new and deleted nodes and blocks. There is a workflow to allow approving all the changes by the end-redaction. While the old site is unaltered they wish to have a live-preview of what the new website will look like.
a Solution? Can Drupal handle this out-of-the-box? An initial guess would be to define a some states using the workflow module and handle revisions using the revision_deletion and revision_moderation modules. But that doesn't help when you want to test drive the site as anonymous visitor. How DID we do it? A small set of bash scripts and drupal modules did the trick. We'd be honoured to explain those and be cross-fired with questions!