[Savannah-cvs] [774] drop obsolete and excessive descriptions

[ineiev]

Revision: 774
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=774
Author:   ineiev
Date:     2024-02-24 12:40:31 -0500 (Sat, 24 Feb 2024)
Log Message:
-----------
drop obsolete and excessive descriptions

Modified Paths:
--------------
    trunk/sviki/FrontEndSetup.mdwn

Modified: trunk/sviki/FrontEndSetup.mdwn
===================================================================
--- trunk/sviki/FrontEndSetup.mdwn      2024-02-24 17:26:40 UTC (rev 773)
+++ trunk/sviki/FrontEndSetup.mdwn      2024-02-24 17:40:31 UTC (rev 774)
@@ -1,12 +1,7 @@
 # Savannah frontend setup
 
 This page describes the configuration needed for Savannah
-new frontend web server and PHP code.
-
-In 2016, the FSF allocated new hardware for Savannah servers,
-kicking off the server migration efforts. The existing server
-(which hosts <http://savannah.gnu.org>) is called `frontend`
-(`frontend.savannah.gnu.org`). The new server is currently
+current frontend web server and PHP code.  The server is
 called `frontend2` (<https://frontend2.savannah.gnu.org>).
 
 Further reading about Savannah server:
@@ -29,12 +24,9 @@
 It uses a MySQL database running on `internal0`.
 
 The code repository is called 'savane', available at
-<http://git.savannah.gnu.org/cgit/administration/savane.git> and
-<git://git.sv.gnu.org/administration/savane.git> (for developers with
-write-access: `git clone
-<USER>@git.sv.gnu.org:/srv/git/administration/savane.git`).
+<http://git.savannah.gnu.org/cgit/administration/savane.git>.
 
-The production machine run the head of the 'frontend'
+The production machine runs the head of the 'frontend'
 branch, see [[Releasing Savane|SavaneReleases]].
 
 For details on how Savane is installed, see [[Savane setup|SavaneSetup]].
@@ -41,28 +33,13 @@
 
 ## Apache/PHP configuration file location
 
-The environment variable `SAVANE_CONF` determines the location of the main
-PHP configuration file for savane. It could be set in Apache configurations
-file (`frontend2:/etc/apache2/sites-available/sv.inc`) or in an `.htaccess`
-file (`/usr/src/savane/frontend/php/.htaccess`) with
-`SetEnv SAVANE_CONF /etc/savane`
+`init.php` accepts a fall-back variable `SV_LOCAL_INC_PREFIX`, which
+is referenced in sites-available/vhosts-nongnu.inc:
+`SetEnv SV_LOCAL_INC_PREFIX /etc/savane/nongnu-conf`.
 
-The `SAVANE_CONF` variable is used in `<savane>/frontend/php/include/init.php`
-to read a hard-coded file named `.savane.conf.php` from the specified 
directory.
+For savannah.gnu.org as opposed to savannah.nongnu.org, `init.php` uses
+the configured default.
 
-`init.php` also accepts a fall-back variable `SV_LOCAL_INC_PREFIX`, which
-is referenced here:
-`sites-available/sv.nongnu.inc:SetEnv SV_LOCAL_INC_PREFIX 
/etc/savane/nongnu-conf`.
-
-** On current production Savannah, none of these are defined for the GNU side 
**
-
-The code in `init.php` falls back to:
-
-     # go back to default location
-     if (file_exists('/etc/savane/.savane.conf.php'))
-        include('/etc/savane/.savane.conf.php');
-
-
 ## "Site-specific" files
 
 Several sections of the displayed HTML