General idea is: Install Magento to Apache's virtual directory, and then modify or add files Magento installation directory.
The result is clear, however, modify the code and the original code mixed together, difficult to manage. In addition, if a team is expanding in the development of Magento, then how should use the version control tools (such as Subvesion) to manage your code?
So my approach is:
I. Separation of Magento extensions (including changes) of the code - into a separate directory.
2. If the original documents relating to the modification of Magento, you have to make that list of files in order to upgrade the system accordingly updated.
3. To use Subversion to manage source code: the daily changes of any tuning is always under a separate project directory, for submission to Subversion, and then Update to the Magento installation directory.
For the first time to update their code to the Magento installation directory, need to perform Subversion, Checkout command. Assuming the directory layout is as follows:
svn / magento
| __ App
| __ Code
| __ Design
Magento installation directory
d: \ programs \ Apache2 \ htdocs \ mageto
svn co http://localhost/svn/magento d: \ programs \ Apache2 \ htdocs \ mageto
Will the code on the checkout svn repository to the d: \ programs \ Apache2 \ htdocs \ mageto directory. This requires d: \ programs \ Apache2 \ htdocs \ mageto directory must be empty, but the directory is Magento installation directory (definitely not empty), so checkout required parameters - force.
svn co - force http://localhost/svn/magento d: \ programs \ Apache2 \ htdocs \ mageto
Can be normal after the update.
* If the first change Magento installation directory under the document, recommended practices are:
In the Magento installation directory to modify the document to be submitted to Subversion, and then in the project directory update. Then as described earlier: has been amended in a separate project directory.
* If checkout prior to the installation directory Mageneto subversion and have the same name as the file Magento installation directory, result is the Magento files under the installation directory will not be updated, but the tag based on the new machine than SVN. One approach is to manually overwrite the old file, another approach is to separate all project work directory files (svn on time should be maintained and consistent, but also. Svn directories) simply copied to the Magento installation directory. Then you can use svn update to work properly
Similarly, for Zen-Cart, Joomla and other developers should encounter a similar problem, how do they solve? May wish to share experiences.