This mail is an automated notification from the support tracker of the project: Savane.
/**************************************************************************/ [support #318] Full Item Snapshot: URL: <http://gna.org/support/?func=detailitem&item_id=318> Project: Savane Submitted by: Mathieu Roy On: mer 22.09.2004 � 22:25 Category: Post-It Priority: 5 - Normal Resolution: None Privacy: Public Assigned to: None Status: Open Release: Summary: Post-It: How do I install Savane? Original Submission: The following should be done: ./configure # build what need to be built make # create the database make database # create the configuration file make conf # install the backend scripts and the translation files make install ---------------------------------------------------------- Then, depending on your setup and expectations, you'll have to tune your configuration (the following comes from the file INSTALL.verbose): INSTALLATION OF SAVANE: This file might change very often. Please make sure you have the most recent version. This installation instructions are still not complete. If you have any questions or run into trouble, please contact us at <https://gna.org/support/?group=savane> $Id: INSTALL.verbose,v 1.20 2004/09/22 08:11:49 yeupou Exp $ * * * FRONTEND AND BACKEND? Savane is made of a PHP Frontend and a Perl Backend. The PHP Frontend is the web interface and the only way to interact with the database and trigger actions executed by the backend. The Perl Backend is a set of scripts that update a system (a set of machines) according to the informations entered in the database by the PHP Frontend. It is not necessary for bug tracking (for instance) because it only relies on the database. It is necessary for mailing lists or CVS because it needs to create directories and configure servers. In the following guide, the tag [BACKEND ONLY] designates information you can skip if you are only interested by the Frontend. * * * GETTING THE SOURCE CODE First, you must get a copy of Savane from the CVS tree located at http://gna.org/projects/savane In this guide, we will assume that your copy is in a directory called /home/products. Go in this directory: cd /home/products (if you use a different directory, keep that in mind every time we refer to /home/products below); The configure script will ask you several things required in order to proceed. You're not forced to choose /etc/savannah as configuration directory. If you choose something else (needed if you use concurrent Savane installation), be sure to set SAVANE_CONF enviroment variable, both in Apache and in terminals you use to call backend scripts. ./configure make It will build several minor parts (translation files etc...) * * * The second step is to create the database: make database * * * CONFFILES: The Savane configuration is made of two files: savannah.conf.pl and savannah.conf.php. savannah.conf.php is generated from savannah.conf.pl, and must not be edited manually. These files should be generated using the script sv_update_conf, for instance by typing: make conf This process may ask for input from user, depending on the informations provided at the configuration step. Each time savannah.conf.pl is edited, run: make update-conf or run the script sv_update_conf to re-generate the savannah.conf.php file. * * * BACKEND INSTALLATION: make install will install backend scripts, even if you only use the frontend. Some backend scripts like sv_update_conf of sv_skill are used for development purposes and must be installed. Also, the translations files will be installed at this step. Note that translation will only work if your server is configured to accept different locales. On Debian, run `dpkg-reconfigure locales` to add more locales. * * * "SKILLS" Savannah users can edit a resume on their profile page. In this resume there is a "Skills" list which values can be obtained from the project CJN (http://sf.net/projects/cjn), by running sv_skill (this command will only work if you accomplished the previous step) * * * [BACKEND ONLY] CRONJOBS: You should edit your /etc/cron.d/savane to fit your needs. This single file runs all the backend jobs. Commands with --cron option will not be effective until you set them on in the configuration file. Remember that backend scripts need SAVANE_CONF to be set if the configuration directory is not /etc/savannah. * * * APACHE CONFIGURATION: Warning: Make sure the env_module is being used by Apache. In the Apache configuration add the following: LoadModule env_module /usr/lib/apache/1.3/mod_env.so - Warning: Make sure that php accept file upload. In the php.ini file, add the following: ; Whether to allow HTTP file uploads. file_uploads = on - Warning: Make sure that php register_globals is set to "on". It is set by default on old PHP packages but not in newer ones. In the php.ini file, add the following: register_globals = on - You can either use a virtual domain for the Savannah package in your server, or you can install it in a subdirectory of your home page. If for instance you are going to install it in a virtual server "projects.my.net" in a server with IP 192.168.62.11, and you've created the configuration file in /etc/savannah/local.inc, you should write the following in Apache's configuration file: NameVirtualHost 192.168.62.11 <VirtualHost 192.168.62.11> ServerName projects.my.net DocumentRoot /home/products/savannah/frontend/php ServerAdmin [EMAIL PROTECTED] AllowOverride All <IfModule mod_env.c> SetEnv SV_LOCAL_INC_PREFIX /etc/savannah </IfModule> </VirtualHost> On the other hand if you decide to install it in a subdirectory of your home URL, for instance http://myhome.net/projects/, and the configuration file is in /etc/savannah/local.inc, put the following lines in Apache's configuration file: Alias /projects /home/products/savannah/frontend/php <IfModule mod_env.c> SetEnv SAVANE_CONF /etc/savannah </IfModule> <Location /projects> AllowOverride All </Location> IMPORTANT: Then reset the Apache server. At this point you should be able to see the Savannah package home page in you server, at the URL where you put it. - If you do not want to AllowOverride (activating .htaccess), you should add something like the following, where PATH is the subdirectory where Savannah is installed (empty if it is in the top directory). <Location PATH/users> SetHandler application/x-httpd-php </Location> <Location PATH/projects> SetHandler application/x-httpd-php </Location> - Note for apache 2.x: St�phane Urbanovski noticed that the following is required for apache 2.x ErrorDocument 404 /404.php # Savannah config file : SetEnv SAVANE_CONF /etc/savannah # php tweaks : php_admin_flag register_globals On php_admin_flag file_uploads On # Disable .htaccess (needed for apache 2.0) : <Location /savannah> AllowOverride None </Location> # Simulate apache 1.3 behavior RewriteEngine on RewriteLog /tmp/rewrite.log RewriteRule ^/savannah/users(.*) /savannah/users?$1 RewriteRule ^/savannah/projects(.*) /savannah/projects?$1 <Location /savannah/users> SetOutputFilter PHP SetInputFilter PHP LimitRequestBody 524288 </Location> <Location /savannah/projects> SetOutputFilter PHP SetInputFilter PHP LimitRequestBody 524288 </Location> * * * [BACKEND ONLY] ANONCVS: You must create anoncvs user and group. * * * CREATING A PROJECT DEDICATED TO ADMINISTRATION Create a user with the web interface and login. You should create a project dedicated to the server administration. Give it the name you chose for it in the configuration. Administrators of this project will be Savannah administrators. Warning: the unix_group_name of the system group MUST be defined in the configuration file before the creation of that group! For detailed info, follow this link: <http://gna.org/support/?func=detailitem&item_id=318> _______________________________________________ Message post� via/par Gna! http://gna.org/ _______________________________________________ Savane-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/savane-dev
