- Getting Started
- Basic Configuration
- Creating Multiple Sites On Your Local Computer
- Error Pages
- Accessing Your Test Site(s)
- Adding Modules and Themes
- Creating Content
- Custom Blocks
- Working with the Menu
- The Contact Form
- URL Aliases
- Moving Entire Drupal Site with Databases
- Moving Stuff to Your Web Site
- Setting Up Cron
- Additional Tips and Tricks
- Categories (Taxonomy)
- Common Problems
- Links and IMG
- Keeping Your Local and Remote Sites Synchronized
- More Reading
- Glossary
Keeping Your Local and Remote Sites Synchronized
Submitted by Nancy on Wed, 02/14/2007 - 00:59.
The point of a test siteA logically grouped set of content - also web site. is to have a place to experiment or develop new content without impacting your users or giving away your latest gee-whiz before its time. But it is also important to make sure that you always have a good working version of your live siteA logically grouped set of content - also web site. on your test siteA logically grouped set of content - also web site..
Let's ignore, for the moment, that in an "ideal" world you will have a staging siteA logically grouped set of content - also web site. which is always identical to the live siteA logically grouped set of content - also web site. and nothing goes live without being staged.
There are two basic techniques for keeping your sites synchronized:
- Manually making sure that the content of the two sites are the same.
- Frequent uploads or downloads of databaseA collection of data related to an application. back ups.
The first technique is quite time consuming and it's difficult to keep user comments on your test siteA logically grouped set of content - also web site.. It also relies on your memory to know what's been changed, unless you update both sites at the same time. If there are things that are dependent on other things (sorry for the technical terminology), you have to be careful that you update them in the right order so that your random visitor doesn't break something.
The second technique allows for user comments to be downloaded to your test siteA logically grouped set of content - also web site.. From there they can be incorporated into the content and deleted, or left as is. You just have to be careful that you don't lose new, experimental, or incomplete content that hasn't been put onto the production siteA logically grouped set of content - also web site. yet.
Which is better? I can't answer that question for you. You need to weigh the risks and benefits and decide that for yourself. Personally, at my age and with my memory, the second technique is probably better for me, at the risk of losing something not yet uploaded. I also have the bad habit of updating things on the live siteA logically grouped set of content - also web site. and not bring the change back to my test siteA logically grouped set of content - also web site..
More to come


pay respect to the original author
Before you post topics you copy and pasted please make a statement about the true author about this article, rather than claiming it as your own, i found this same article in DRUPAL
Drupal
An open-source content management system that is used on this site and is taking over the world.Yes, you did
Yes, you did see it, and the rest of this cookbook on drupal
Drupal
An open-source content management system that is used on this site and is taking over the world..org. And if you check you will see that I am the original author and that posting dates on this web siteA logically grouped set of content - also web site. predate those. And, BTW, I do respect myself.Good reasoning
Thanks for this little tutorial. Good reasoning. Will contine explore your siteA logically grouped set of content - also web site. and tips.
Thanks
Thank you for stopping by.