[documentation] [Documentation task] Proposal: "HOWTO: Make changes to the code without disrupting a live site"

[SpzToid]

Issue status update for 
http://drupal.org/node/60911
Post a follow up: 
http://drupal.org/project/comments/add/60911

 Project:      Documentation
 Version:      <none>
 Component:    Installation
 Category:     tasks
 Priority:     normal
 Assigned to:  njivy
 Reported by:  njivy
 Updated by:   SpzToid
 Status:       active

Please refer to step two in this page: (http://drupal.org/node/26434).
Is this what you had in mind?


Please note I removed this step 2 from the options I otherwise
detailed, in the 'multiple sites' version of this document (scroll to
the bottom): http://drupal.org/node/47163


If you would like me add/clarify this to the mulitple-sites docs
(linked 2nd, this message), tell me so, be patient, and I'll get it
done. I'll do it, but I struggle getting my head 'round with this
RewriteBase stuff, so please be patient. In the meantime, maybe the
first link in this message will help you.




SpzToid



Previous comments:
------------------------------------------------------------------------

Fri, 28 Apr 2006 19:49:20 +0000 : njivy


* *Objective*: Explain how to make changes to the code without
disrupting activity on a live Drupal site
* *Audience*: Site administrators with command-line access and skill
* *Topics covered*:

* Create a special .htaccess file
* Partition the directory for different instances of Drupal
* Edit Drupal in a couple places to accommodate the partitioning
* Use symlinks to tie it all together


* *Topics not covered*:

* How to use the command line
* Install Drupal from CVS or tarball
* Duplicate the database
* Accommodate environments without mod_rewrite
* Accommodate environments without symlinks


* *Other future related documentation*:

* HOWTO: Update the code base of a live site with no down time (less
than a second, actually)
* HOWTO: Test code and theme changes randomly (i.e. perform A/B
testing)


* *Questions*:

* Does someone else have experience in these topics?  I'd like to chat
with them and compare notes.
* Where can I maintain the documentation until it's ready and accepted?
 Is a Writeboard [1] okay?


[1] http://writeboard.com/