[Savannah-cvs] [573] remove obsolete passage

[ineiev]

Revision: 573
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=573
Author:   ineiev
Date:     2023-02-09 06:20:06 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
remove obsolete passage

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

Modified: trunk/sviki/FrontEnd.mdwn
===================================================================
--- trunk/sviki/FrontEnd.mdwn   2023-02-09 11:16:23 UTC (rev 572)
+++ trunk/sviki/FrontEnd.mdwn   2023-02-09 11:20:06 UTC (rev 573)
@@ -1,25 +1,14 @@
-Savannah front-end
-==================
-The Savane front-end is installed on the 'frontend' virtual machine, in
+# Savannah frontend
+
+The Savane frontend is installed on the 'frontend' virtual machine, in
 `/usr/src/savane/`, which pulls from the `administration/savane.git`
 repository.
 
-Some of the content is configurable, using text files that are stored in
-the webcvs repository for `administration`.
-<http://web.cvs.savannah.gnu.org/viewvc/administration/content/?root=administration>
-The live CVS checkout is at `frontend0:/etc/savane/content`.
+## Web server restarts
 
-After committing changes in either of those repositories, to make the
-changes live, it is necessary to log in to frontend and manually `git
-pull` or `cvs update` in the live checkout directory.  There are no
-automated updates of the live checkouts (and thus they often lag behind
-the repository; if you see this, please deal with it).
-
-Web server restarts
--------------------
 To restart the web server (on any of the hosts running one), the usual
 `service apache2 restart` should do it, or `service apache2 reload` if
-you wish.  Of course you should check the sites before and after
+you wish.  Of course, you should check the sites before and after
 restarting, to make sure things are working.  There are no
 password-protected SSL keys on Savannah, so that the web servers can
 come up unattended at boot.