savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...


From: Sylvain Beucler
Subject: [Savannah-cvs] administration/docs/hacking_savannah hacking_sa...
Date: Mon, 01 Nov 2004 09:27:21 -0500

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/11/01 14:21:47

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Added paragraph about SSL == 1 IP per hostname
        Added a configuration trick to ease the nongnu maintenance.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.64&tr2=1.65&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.64 
administration/docs/hacking_savannah/hacking_savannah.texi:1.65
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.64     Mon Nov 
 1 12:35:32 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Mon Nov  1 
14:21:47 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.64 2004/11/01 12:35:32 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.65 2004/11/01 14:21:47 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -1026,7 +1026,26 @@
 $ make update-conf
 @end example
 
-[TODO: how to do that for nongnu-conf]
+
+To make the non-GNU conf easy to maintain, you can use this 
@file{savannah.conf.php} file:
address@hidden
+<?php
+include "/etc/gnu-conf/savannah.conf.php";
+      $sys_default_domain="savannah.nongnu";
+      $sys_https_host="$sys_default_domain";
+      $sys_brother_domain="savannah.gnu";
+      $sys_incdir="/etc/nongnu-content";
+      $sys_lists_domain="$sys_default_domain";
+?>
address@hidden verbatim
+
+It is seems it is very BAD to add a new line at the end of the file (I
+think, especially for p and pr that are doing body-less HTTP
+redirections) - to be tested.
+
+You can also delete the savannah.conf.pl from nongnu.conf, since it is
+never used.
+
 
 Be sure that the @file{savannah.conf*} files have proper permissions:
 @example
@@ -1036,6 +1055,7 @@
 @end example
 for both gnu-conf and nongnu-conf.
 
+
 Also update the skills list:
 @example
 $ /usr/local/savane/bin/sv_skill
@@ -1053,6 +1073,11 @@
 The symbolic links are created this way so as to avoid following
 symlinks outside the WWW root.
 
+[TODO: I recommand against this configuration, since it makes you
+update the files directly served by Apache. I suggest to work in
+/usr/src/savane and do a @command{cp -a} once your CVS work is done.]
+
+
 
 Currently, some files from the sysadmins requires a Setuid backport
 from Perl 5.8 to Perl 5.6.
@@ -1110,6 +1135,9 @@
 NameVirtualHost savannah.gnu:80
 NameVirtualHost savannah.gnu:443
 @end example
+Keep in mind, though, that you will get a warning when going to
+nongnu, since SSL works at the OSI presentation layer, not the
+application one, ie you need an IP per hostname.
 @end itemize
 
 Now, you need to tune the Savannah configuration files to your




reply via email to

[Prev in Thread] Current Thread [Next in Thread]