Relation between source and destination servers
RdeBoer - July 8, 2009 - 05:14
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi,
Looks like a great module!
Having read the installation instructions I wondered about the following.
Is it necessary for the source and destination installations (in particular the databases) to be based on a common ancestor?
Or is it possible to copy content across from source to destination even when the destination was never created as a clone from the source?
#1
- subscribing
I would also be interested in the answer to this. My use case would be.
1. Sally sets up a "sandbox" Drupal installation on their local machine
2. She creates several nodes (content type article) on the "sandbox" machine containing, say for example, book reviews.
3. Tom sets up a public Drupal site where he publishes articles that interest him. He would like to include Sally's book reviews
4. Sally uses the Deploy module to push her book reviews from her local "sandbox" to Tom's public site.
Can this be done with Deploy?