[Savannah-cvs] [805] updates on config files and source code offer

[ineiev]

Revision: 805
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=805
Author:   ineiev
Date:     2024-10-09 11:41:40 -0400 (Wed, 09 Oct 2024)
Log Message:
-----------
updates on config files and source code offer

Modified Paths:
--------------
    trunk/sviki/SavaneConfiguration.mdwn
    trunk/sviki/SavaneReleases.mdwn
    trunk/sviki/SavaneSetup.mdwn

Modified: trunk/sviki/SavaneConfiguration.mdwn
===================================================================
--- trunk/sviki/SavaneConfiguration.mdwn        2024-09-27 15:48:20 UTC (rev 
804)
+++ trunk/sviki/SavaneConfiguration.mdwn        2024-10-09 15:41:40 UTC (rev 
805)
@@ -2,16 +2,20 @@
 
 ## System
 
-It's in:
+It's in files normally located in /etc/savane/:
 
-- /etc/savane/savane.conf.pl
-- /etc/savane/savane.conf.php
-- /etc/savane/savane.ini
-- /etc/savane/membersh-conf.pl
+- savane.conf.pl
+- savane.conf.php
 
 in all VMs that use Savane. Keep them in sync (especially the database
 password).
 
+
+Some files are used (as of 2024-09) in donwload:
+
+- membersh-conf.pl
+- mirmon-to-geoip.conf 
+
 ## Frontend customization
 
 The texts embedded in the web interface are stored at

Modified: trunk/sviki/SavaneReleases.mdwn
===================================================================
--- trunk/sviki/SavaneReleases.mdwn     2024-09-27 15:48:20 UTC (rev 804)
+++ trunk/sviki/SavaneReleases.mdwn     2024-10-09 15:41:40 UTC (rev 805)
@@ -32,10 +32,13 @@
 The requirement of the AGPL to offer the corresponding source code
 is triggered in these cases:
 
-- The PHP code of Savannah Web UI.  Savane links to the respective commit
-  at our Cgit instance (the "Corresponding source code" link at the bottom
-  of the page).  Keeping the frontend branch at the specific commit makes sure
-  that it is accessible and git gc doesn't remove it.
+- The PHP code of Savannah Web UI.  When Savane is built, a distribution 
tarball
+  is generated and installed next to PHP files.  Normally, Savane serves that
+  file as the "Corresponding source code" link at the bottom of the page;
+  as a fallback for the non-realistic case when the tarball is absent, a link
+  to the respective commit at our Cgit instance is provided.  Keeping the 
frontend
+  branch at the specific commit makes sure that it is accessible and git gc 
doesn't
+  remove it.
 - The sv_membersh script for SSH access, as of 2024-04 used at the download
   server.  The source code of Savane is provided from the same machine through
   RSYNC, which is one of the protocols offered for downloading the hosted data.

Modified: trunk/sviki/SavaneSetup.mdwn
===================================================================
--- trunk/sviki/SavaneSetup.mdwn        2024-09-27 15:48:20 UTC (rev 804)
+++ trunk/sviki/SavaneSetup.mdwn        2024-10-09 15:41:40 UTC (rev 805)
@@ -1,6 +1,6 @@
 # Savane setup
 
-As of 2024-02, Savane is installed and runs on mgt1, download0,
+As of 2024-09, Savane is installed and runs on mgt1, download0,
 vcs0, vcs1, vcs2, frontend2.  The installation procedure
 is quite uniform.
 
@@ -46,27 +46,25 @@
 
 ### frontend
 
-The only machine where --disable-frontend is *not* used; --enable-changelog
-is also not used because the source code is offered via Cgit.
+The only machine where --disable-frontend is *not* used.
 
 ### mgt
 
 The users don't interact with this machine, no access is provided,
-so the source code isn't offered, and --enable-changelog isn't needed here.
+so the source code isn't offered.
 
 ### vcs
 
 The offer from sv_membersh suggests an rsync option that omits the '.git'
-directory, so --enable-changelog is used as a way to list the changes made
-in original software. (As of 2024-04, sv_membersh isn't used on vcs
-machines, but that doesn't invalidate the Savane setup above
+directory, so a ChangeLog is generated from Git logs as a way to list
+the changes made in original software. (As of 2024-09, sv_membersh isn't
+used on vcs machines, but that doesn't invalidate the Savane setup above
 and the possibility to get the corresponding source code of the running
 instance.)
 
 ### download
 
-In addition to --enable-changelog discussed in the preivous section,
-the configure script runs with --enable-mirror, that switches on
+The configure script runs with --enable-mirror, that switches on
 mirror-redirect and other mirror-related scripts.
 
 ---