gforge/docs/architecture/tour/next1.gif svneol=native#unset
gforge/docs/architecture/tour/prev0.gif svneol=native#unset
gforge/docs/architecture/tour/prev1.gif svneol=native#unset
-gforge/docs/branching.sda svneol=native#unset
gforge/docs/images/sflogo2-105a.png -text
gforge/docs/project_management/source_branching.sda svneol=native#unset
-gforge/docs/sourceforge-architecture.sda svneol=native#unset
gforge/www/bugs/bugs-er-diagram.sda svneol=native#unset
gforge/www/forum/forum-er-diagram.sda svneol=native#unset
gforge/www/images/404.png svneol=native#unset
+++ /dev/null
-
-SourceForge 2.5 Installation notes
-----------------------------------
-
-ALL INSTALL QUESTIONS SHOULD BE ASKED IN THE FORUM:
-http://sourceforge.net/forum/forum.php?forum_id=21304
-
-
-The most important change you will notice in the 2.5 code
-release is that we now require PostgreSQL 7.1beta or higher.
-Mysql does NOT support transactions or subselects, so the
-site will not function correctly. Foundries depend on
-subselects - if you don't need foundries you can still use
-MySQL. Future versions of the code will be completely
-dependent on subselects, views, etc.
-
-You can see in the www/include/ directory that there are
-database abstraction layers for pgsql, mysql and Oracle 8.
-The oracle 8 layer is COMPLETELY untested. It hasn't been
-executed even once.
-
-
-Migrating an existing install:
-------------------------------
-
-Moving to 2.5 from 2.0x (mysql) is complex, but not impossible.
-Here's how we did it on SourceForge.net:
-
--Download, install, and configure PostgreSQL 7.1+
--Apply all changes to your existing MySQL database
- (mysql -u root -p db_name < SQL_diff-2.0-to-2.5.sql)
--Dump your MySQL database using mysqldump with the --tab option:
- mysqldump -q --tab=/tmp/dbfiles/ -u root -p db_name
--Create a new PostgreSQL database:
- createdb db_name
--Create the tables and sequences in your new database:
- psql db_name < pgport/Sourceforge.sql92
--Edit the file in pgport/Sourceforge.init and change the
- COPY TABLE commands to draw the files from wherever
- you dumped them to in the mysqldump step
--Run the Sourceforge.init script into your new database:
- psql db_name < pgport/Sourceforge.init
--Then vacuum the postgres database:
- psql db_name
- % vacuum analyze;
--Edit your /etc/local.inc to set the right params to connect
- to your new postgresql database
-
-
-Setting up a new install:
--------------------------
--Download, install, and configure PostgreSQL 7.1+
--Create a new PostgreSQL database:
- createdb db_name
-Run the Sourceforge.sql script into your new database:
- psql db_name < Sourceforge.sql
--Then vacuum the postgres database:
- psql db_name
- % vacuum analyze;
--Install and edit the etc/local.inc to set the right params to connect
- to your new postgresql database, host vars, etc
--Import the default values file into the database.
- psql db_name < DefaultValues.sql
- Constraints and other problems may prevent this from working
- seamlessly.
-
+++ /dev/null
-<HTML>
-<HEAD>
-<TITLE>SourceForge Documentation Project: SourceForge-1.0.4 Administrator Guide</TITLE>
-</HEAD>
-<BODY bgcolor="#FFFFFF">
-
-<TABLE>
-<TR valign="bottom">
-<TD><A href="http://sourceforge.net"><IMG src="images/sflogo2-105a.png" border=0></A></TD>
-<TD><FONT size="+1" face="arial,helvetica">SourceForge Documentation Project</FONT>
-<BR><FONT face="arial,helvetica"><I>Maintained by SourceForge Volunteers</I>
-
-<P>Current Document: <B>SourceForge-1.0.4 Administrator Guide</B>
-
-<P>Go to: <A href="http://sfdocs.sourceforge.net/">[SFDocs Home]</A>
-<A href="http://sourceforge.net/project/?group_id=873">[SourceForge Project Page]</A>
-<A href="http://sourceforge.net/">[SourceForge.net]</A>
-
-</FONT>
-</TD></TABLE>
-<HR>
-<p>This is an administrator guide to the SourceForge software as found
-on <a href=http://sourceforge.net/project/?group_id=1>SourceForge</a>.
-It gives hints to successfully create a SourceForge service on a machine.
-It assumes that you've successfully installed the software as described
-in <a href="Install_Guide.html">SourceForge-1.0.4 Installation Guide</a>
-
-<pre>
--------------------------------------------------------------------------------
-Create the admin user
-
-Before trying anything you must create a user named admin. This user will
-automatically be assigned server wide administration permissions. On the
-home page a Site Administrator menu should appear.
-
--------------------------------------------------------------------------------
-Create categories
-
-Unless some categories exist in the software map you won't be able to create
-a new project. Create one or two categories using the Site Administrator menu.
-
--------------------------------------------------------------------------------
-Populate the project_status table
-
-This table lists the possible status of a task in the Task Manager. If it
-is not filled the status of a task will be assigned a random value and will
-therefore disapear from the task lists.
-
-insert into project_status (status_name) values ('Open');
-insert into project_status (status_name) values ('Closed');
-insert into project_status (status_name) values ('Deleted');
-
--------------------------------------------------------------------------------
-Default IDs
-
-id=100 is used throughout the site as a default. user_id=100 is for a
-user named "none", which is referenced a lot. bug_group_id=100 is a
-default adefault as well. There are instances throughout the patch
-manager, surveys, bugs, and task manager where this is used, as an
-FYI. Also bug_status, patch_status, project_status are tables (maybe
-more), that we need to include default data for.
-
-</pre>
-
-<P><HR><P><pre><font size=-1>$Id: Adminstration_Guide.html,v 1.1 2000/05/04 18:45:01 precision Exp $</font></pre><br>
-</BODY>
-</HTML>
+++ /dev/null
-<HTML>
-<HEAD>
-<TITLE>SourceForge Documentation Project: SourceForge-1.0.4 Contributor Guide</TITLE>
-</HEAD>
-<BODY bgcolor="#FFFFFF">
-
-<TABLE>
-<TR valign="bottom">
-<TD><A href="http://sourceforge.net"><IMG src="images/sflogo2-105a.png" border=0></A></TD>
-<TD><FONT size="+1" face="arial,helvetica">SourceForge Documentation Project</FONT>
-<BR><FONT face="arial,helvetica"><I>Maintained by SourceForge Volunteers</I>
-
-<P>Current Document: <B>SourceForge-1.0.4 Contributor Guide</B>
-
-<P>Go to: <A href="http://sfdocs.sourceforge.net/">[SFDocs Home]</A>
-<A href="http://sourceforge.net/project/?group_id=873">[SourceForge Project Page]</A>
-<A href="http://sourceforge.net/">[SourceForge.net]</A>
-
-</FONT>
-</TD></TABLE>
-<HR>
-<p>This is an contributor guide to the SourceForge software as found
-on <a href=http://sourceforge.net/project/?group_id=1>SourceForge</a>.
-It explains how contributors should behave in order to see their
-patches accepted by the administrators of the project.
-It assumes that you've successfully installed the software as described
-in <a href=Install_Guide.html>SourceForge-1.0.4 Installation Guide</a> and
-that you're running your own instance as explained in <a href=Adminstration_Guide.html>SourceForge-1.0.4 Administrator Guide</a>
-
-<P>
-You must understand that integration of any kind of modification to the
-code is subject to carefull reviewing by the SourceForge team. They will
-ultimately be responsible for bugs or security problems, not you. At
-present patches are processed using the patch manager and it is expected
-that <b>very</b> few people will have write access to the CVS repository.
-
-<P>
-At present no software roadmap exists and no regression tests are implemented
-and therefore the following rules cannot apply fully. Hopefully a contributor
-will make these two happen.
-
-<P><B>Etiquette</B><P>
-
-<UL>
-<LI> Whatever your coding style is, mimic exactly the existing
- style. Period. Here are some hints:
- <UL>
- <LI> Use tabulations instead of white space for indentation.
- </UL>
-<LI> Fully review the code roadmap before modifying anything.
- If you discover things that are not in the roadmap, contribute to
- the roadmap document with updates or additions.
-<LI> Search carefully the forums and mailing list archives for discussions
- related to the contribution/bugfix you're willing to make.
-<LI> Read all the code in www/include at least once and understand its
- purpose. This is the library and you don't want to re-implement anything
- it contains.
-<LI> Always update the ChangeLog file and be very precise.
-</UL>
-
-<P><B>New functionalities</B><P>
-
-So, you're absolutely sure the functionality is not already implemented,
-that it's not a task in progress. You should now convince at least one
-person in the developper community that it's worth doing.
-<P>
-Describe what you're planning to do in the forum.
-Precisely describe algorithms, functionalities. Wait for approval from
-another developper. In the meantime you can implement what you have in
-mind.
-<P>
-
-<UL>
-<LI> Add the task in the task list and update daily.
-<LI> Implement the functionality.
-<LI> Write a non-regression test for it.
-<LI> Run the non-regression tests for all the software until it says ok.
-<LI> Update the SourceForge documentation and roadmap to describe the new functionality.
-</UL>
-
-<P><B>Bug Fixing</B><P>
-
-<UL>
-<LI> Assign the bug to yourself in the bug list. Never work on a bug
- assigned to someone else, unless you're talking to the other
- developper.
-<LI> Write a non-regression test for it. Should it pop again, the test
- must detect it.
-<LI> Fix the problem.
-<LI> Run the non-regression tests for all the software until it says ok.
-</UL>
-
-<P><HR><P><pre><font size=-1>$Id: Contributor_Guide.html,v 1.1 2000/05/04 18:45:01 precision Exp $</font></pre><br>
-</BODY>
-</HTML>
+++ /dev/null
-<HTML>
-<HEAD>
-<TITLE>SourceForge Documentation Project: SourceForge-2.0 Installation Guide</TITLE>
-</HEAD>
-<BODY bgcolor="#FFFFFF">
-
-<TABLE>
-<TR valign="bottom">
-<TD><A href="http://sourceforge.net"><IMG src="images/sflogo2-105a.png" border=0></A></TD>
-<TD><FONT size="+1" face="arial,helvetica">SourceForge Documentation Project</FONT>
-<BR><FONT face="arial,helvetica"><I>Maintained by SourceForge Volunteers</I>
-
-<P>Current Document: <B>SourceForge-2.0 Installation Guide</B>
-
-<P>Go to: <A href="http://sfdocs.sourceforge.net/">[SFDocs Home]</A>
-<A href="http://sourceforge.net/project/?group_id=873">[SourceForge Project Page]</A>
-<A href="http://sourceforge.net/">[SourceForge.net]</A>
-
-</FONT>
-</TD></TABLE>
-<HR>
-<p>This is an installation guide for the SourceForge software as found
-on <a href=http://sourceforge.net/project/?group_id=1>SourceForge</a>.
-This is not yet complete but allows to experiment everything not involving
-DNS, CVS, cvsweb, ftp.
-
-<pre>
--------------------------------------------------------------------------------
-Creating the MySQL database (assuming MySQL version >= 3.22.25)
-
-1) Install MySQL from http://www.mysql.com/
-
-2) Choose a database name (let's say 'sourceforge' for the rest of
- this document).
-
- mysql -e "create database sourceforge"
-
-3) Create the tables.
-
- mysql sourceforge < db/SourceForge.sql
-
--------------------------------------------------------------------------------
-Configuring Apache with SSL (assuming Apache version >= 1.3.9
- openssl version >= 0.9.4
- mod_ssl version >= 2.4.10-1.3.9)
-
-The best starting point is http://www.modssl.org/. There is very
-little chance that your installed Apache server contains SSL, you'll
-have to recompile and reinstall. I highly recommend to install Apache
-it in a non-standard place. It won't interfere with your working
-Apache, if any. And, more important, the installation process will
-install sample configuration files instead of keeping them in the
-source directory because you already have some installed.
-
-1) Install openssl
-
-2) Configure mod_ssl
-
-3) Install Apache
-
--------------------------------------------------------------------------------
-Configuring Apache with PHP (assuming Apache version >= 1.3.9 and
- php version >= 4.0)
-
-1) Create a file in the Apache document root named phpinfo.php
-
- echo '<? phpinfo(); ?>' > .../phpinfo.php
-
- Try to load it with your browser using http://localhost/phpinfo.php.
- If it shows an HTML page you already have php installed.
- If the page shown contains the word MySQL you have php compiled
- with MySQL support.
- If you see the page and find MySQL in it, you're finished with this
- chapter. Otherwise proceed to the following steps.
-
-2) Make sure php4 is compiled in (note - SourceForge no longer works with php3).
- Try to access http://localhost/server-info and search for php. If
- it's found somewhere in the page, the php module is available.
- If http://localhost/server-info does not work add the following lines to
- the access.conf file:
-
- #
- # Allow remote server configuration reports, with the URL of
- # http://servername/server-info (requires that mod_info.c be loaded).
- # Change the ".your_domain.com" to match your domain to enable.
- #
- <Location /server-info>
- SetHandler server-info
- Order deny,allow
- Deny from all
- Allow from localhost
- </Location>
-
- If you did not find php you'll have to recompile it yourself. See
- http://www.php.net/ and remember that you must re-compile php with
- MySQL support.
-
-3) Activate php.
-
- In order to activate php the following lines must be found in the
- httpd.conf file:
-
- LoadModule php_module modules/libphp.so
- AddModule mod_php.c
-
-4) Enable index.php as a directory index in srm.conf.
-
- DirectoryIndex index.html index.shtml index.cgi index.php
-
-5) Add .php extension to srm.conf.
-
- AddType application/x-httpd-php .php
- AddType application/x-httpd-php-source .phps
-
-6) Try loading http://localhost/phpinfo.php again.
-
--------------------------------------------------------------------------------
-Configuring php and Apache for SourceForge
-
-1) Change the DocumentRoot
-
- Since some scripts assume that the document root starts at the
- www directory, just say that the document root is this directory.
-
- In srm.conf
-
- DocumentRoot /home/loic/local/ports/alexandria/www
-
- In access.conf substitute/clone the <Directory> block for the
- new document root.
-
-2) Type the URL http://localhost/ in your navigator.
-
- You should see an error message like this:
-
- Fatal error: Failed opening required 'pre.php' in /home/httpd/html/sf/index.php on line 9
- meaning that Apache is properly configured as far as php is concerned.
-
-3) Specify the include path.
-
- You must tell php where the include files are. Add the full path to
- ../alexandria/www/include to the include_path variable of the
- php.ini file. Something like
-
- include_path = /home/php:/home/loic/local/ports/alexandria/www/include
-
- Alternatively you can add the following lines in httpd.conf:
-
- <Directory />
- php_value include_path "/usr/local/htdocs/alexandria/www/include:."
- </Directory>
-
-4) Include magic in php.ini.
-
- magic_quotes_gpc = On ; magic quotes for incoming GET/POST/Cookie data
- magic_quotes_runtime = Off ; magic quotes for runtime-generated data, e.g. data from SQL,
- track_vars = On ; enable $HTTP_GET_VARS[], $HTTP_POST_VARS[] and $HTTP_COOKIE_VARS[] arrays
-
-5) Restart httpd
-
-6) Type the URL http://localhost/ in your navigator. Two things
- may happen at that point:
-
- a) You're redirected to http://sourceforge.net/ since that's what the library does
- when you're not using localhost in the URL.
-
- b) You see an error message like this:
-
- Fatal error: Failed opening required '/etc/local.inc' in database.php on line 11
-
- In either cases it means that the pre.php file was found and that the include
- path is correct.
-
--------------------------------------------------------------------------------
-Configuring SourceForge
-
-1) Create the /etc/local.inc file with the following:
-
- <?php
-
- $sys_dbhost="your_db_host_name";
- $sys_dbname = "sourceforge";
- $sys_dbuser="user_name";
- $sys_dbpasswd="your_password";
- $sys_server="mysql";
-
- //
- // With a trailing /
- //
- $sys_urlroot="/path/to/www/doc/root/";
- $sys_name="web1";
- ?>
-
-2) Look at the home page http://localhost/
- It should display well.
-
-3) Create a user named admin
-
- This user will automatically be assigned server wide administration permissions.
-
-
-</pre>
-
-<P><HR><P><pre><font size=-1>$Id: Install_Guide.html,v 1.2 2000/10/27 18:44:40 pfalcon Exp $</font></pre><br>
-</BODY>
-</HTML>