[cvs] [Wiki] changed: ReleaseManagement

[Michael Slusarz]

slusarz  Tue, 22 Dec 2009 23:21:12 -0500

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.35
Change log:  new dev install script

@@ -81,46 +81,17 @@
  **Q:** Are we going to keep the existing development model where we  
have a "master" server (i.e. cvs.horde.org) where we will build the  
releases?  For our workflow, that seems to make the most sense - since  
we don't have a "master" user that checks all commits before  
integrating.

  **A:** Yes. All HEAD commits are pushed to  
dev.horde.org:/horde/git/horde (or horde-hatchery, etc.), and we'll  
use branches to do local dev or to coordinate non-mainline work.

-**Q:** How do I start from scratch with a git/cvs head install
-
-**A:** Note that if this is the first time you've dealt with our  
framework libraries, you will need to discover our PEAR server before  
proceeding with the steps below:
-<code>
-pear channel-discover pear.horde.org
-</code>
+**Q:** How do I start from scratch with a Git install

+**A:** You will need to download the two Git repositories:
  <code>
  git clone --depth 1 git://dev.horde.org/horde/git/horde horde-git
  git clone --depth 1 git://dev.horde.org/horde/git/horde-hatchery
-cd horde-git/horde
-mkdir libs
-echo "<?php ini_set('include_path', dirname(__FILE__) . '/../libs' .  
PATH_SEPARATOR . ini_get('include_path'));" > lib/core.local.php
-horde-fw-symlinks.php --src ../framework
-horde-fw-symlinks.php --src ../../horde-hatchery/framework
  </code>

-Then continue with the installation steps in docs/INSTALL. Set the  
paths to the various Horde applications via the 'fileroot' and  
'webroot' parameters in config/registry.php. If these directories do  
not live directly under git, you must create a config/horde.local.php  
file in this application and define HORDE_BASE in that file like this:
-
-<code>
-<?php
-define('HORDE_BASE', '[Full filesystem path to horde]');
-</code>
-
-After some time has passed you will want to update your working copy  
from the Horde servers. These commands will do that. The commands are  
to be executed from the base of the Horde installation (in the above  
setup, horde-git/horde):
-
-<code>
-git pull --rebase
-git --git-dir=../../horde-hatchery/.git  
--work-tree=../../horde-hatchery/ pull --rebase
-</code>
-
-Now we have to refresh the Framework library symlinks:
-
-<code>
-rm -rf libs/*
-php ../framework/devtools/horde-fw-symlinks.php
-php ../framework/devtools/horde-fw-symlinks.php --src  
../../horde-hatchery/framework
-</code>
+Creating a web-accessible installation can be done simply by running  
the install_dev PHP script (located at horde-git/framework/bin in the  
repository checked out above).  To run this script, copy  
horde-git/framework/bin/install_dev.conf.dist to  
horde-git/framework/bin/install_dev.conf and edit that file to match  
the setup of your server.  Running that script will symlink the entire  
horde package into the web-accessible directory you specify, symlink  
all other horde applications within that directory, and will properly  
set up the necessary include/horde path definitions. Note that all  
edits should take place within the repository, as the horde directory  
will be deleted every time the install_dev script is run.  
Additionally, full directory paths will be needed in the  
horde/config/registry.php file due to the symlinks.

  **Q:** Why does the sidebar not collapse/Why can't I switch tabs on  
the config screen/Why do certain links not work?

  **A:** Make sure your 'jsfs' and 'jsuri' entries in  
horde/config/registry.php are correct. They are actually no needed  
anymore at all, unless you really know what you are doing.  
Applications no longer come shipped with javascript source files in  
js/src - they all live directly under js/ now.