Documentation #1589

Clone drupal website

Added by herck over 4 years ago. Updated about 4 years ago.

Status:ArchivedStart date:11 Aug 2016
Priority:NormalDue date:
Assignee:herck% Done:


Target version:Sprint32


The idea is to have two separate drupal websites:
-the one that is publicly available under our current web address
-one that we use to put all the updates for the next release (python examples, API changes, ...)
During release, we switch the publicly available one from Apache and clone back for the next release.

Investigate the maintenance cost for the cloning/switching during each release.


#1 Updated by herck over 4 years ago

After some investigation, it seems that switching between two drupal sites is not the most effective way of achieving bulk publishing during releases. There are modules, like Workbench Moderation and Views Bulk Operations, that can do this. We have to postpone the implementation and configuration of these modules for a while however, since:
-We first have to clone the current site to be able to do a safe upgrade to drupal 8 (I will name the folder for the new site drupal8).
-After switching to the drupal 8 website, we can then look at how we will manage bulk operations during release with the appropriate modules.

#2 Updated by herck over 4 years ago

  • Status changed from Sprint to Resolved

Clone now on:

#3 Updated by herck about 4 years ago

  • Status changed from Resolved to Archived

Also available in: Atom PDF