[Savannah-cvs] [179] mention curl command to trigger web page updates, and update explanation of cvs-only for web pages

[karl]

Revision: 179
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=179
Author:   karl
Date:     2016-02-08 01:03:48 +0000 (Mon, 08 Feb 2016)
Log Message:
-----------
mention curl command to trigger web page updates, and update explanation of 
cvs-only for web pages

Modified Paths:
--------------
    trunk/sviki/HomePage.mdwn
    trunk/sviki/HomepageUpload.mdwn

Modified: trunk/sviki/HomePage.mdwn
===================================================================
--- trunk/sviki/HomePage.mdwn   2016-01-17 00:05:02 UTC (rev 178)
+++ trunk/sviki/HomePage.mdwn   2016-02-08 01:03:48 UTC (rev 179)
@@ -1,32 +1,34 @@
--   nongnu: www.nongnu.org/project/ and project.nongnu.org
--   gnu: gnu.org/software/project (shortcut gnu.org/s/project)
+Web pages for Savannah projects
+===============================
+Each project at Savannah has a "web pages" repository, completely
+separate from the "sources" repository.  These are the standard urls
+provided:
 
+- For gnu projects: gnu.org/software/project/ (shortcut: gnu.org/s/project/)
+- For nongnu projects: www.nongnu.org/project/ and project.nongnu.org/
+
 No symlinks (sysadmin@ says: "security reasons" and "there's also the
 fact that CVS doesn't handle symlinks") - use .symlinks instead. Add a
 file named .symlinks in each directory where you want to make symbolic
 links. Each line of the file lists a real file name followed by the name
 of the symbolic link. The symbolic links are built every hour.
 
-No .htaccess either, for the same reason - it would allow to bypass this
+No .htaccess either, for the same reason - it would allow bypassing this
 symlinks setup (based on mod\_rewrite).
 
-Using a new VCS
----------------
+Initial upload of web pages: [[HomepageUpload]].
 
-This is not trivial because all of www.gnu.org is stored and managed in
-CVS, with multiple repositories.
+Basic CVS usage: [[CvsGettingStarted]].
 
-At a point, GNU webmasters needed the privilege to edit any CVS web
-repository. However they now don't edit these repositories directly
-anymore, so we don't need to implement this requirement anymore.
+Using a different VCS
+---------------------
+Many people have requested using something other than CVS for their web
+page repositories.  This is not unreasonable, but requires substantial
+frontend work, backend work, and coordination with the FSF sysadmins.
+There is no ETA for any of this.  There are far more urgent problems in
+the Savannah infrastructure at present, and nowhere near enough
+volunteer hours to do them.
 
-This post explains how Fedora moved from CVS to Git in 2010 for their 1K
-package repositories (with shared state). We probably can do it for
-www.gnu.org too.
-<http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000647.html>
+Meanwhile, perhaps git-over-cvs could be used, but we have no experience
+with this.
 
-Such a change would require coordination with the FSF sysadmins, who run
-www.gnu.org.
-
-www.nongnu.org however might be moved to Savannah if necessary so we
-make changes directly to the replication process.

Modified: trunk/sviki/HomepageUpload.mdwn
===================================================================
--- trunk/sviki/HomepageUpload.mdwn     2016-01-17 00:05:02 UTC (rev 178)
+++ trunk/sviki/HomepageUpload.mdwn     2016-02-08 01:03:48 UTC (rev 179)
@@ -1,13 +1,19 @@
-In fact, it works like importing your project into the CVS Sources: for
-the homepage we use the CVS tree called web.
+Upload project web pages
+========================
 
-1.  First, you need to configure your SSH access - (see [[SshAccess]]).
+See [[Homepage]] for general info on the per-project web pages.
 
+To import an initial setup web pages for your project, use the `web`
+repository (this is completely separate from any source trees).  The web
+tree always uses CVS.  For basic CVS usage, see [[CvsGettingStarted]].
+
+1.  First, you need to configure your [[SshAccess]].
+
 2.  You should have read instructions in your CVS project page on
-    savannah (like the emacs CVS page
+    savannah (e.g., the emacs CVS page is
     <http://savannah.gnu.org/cvs/?group=emacs>).
 
-3.  You should go in the local directory where you want to put your
+3.  Go to the local directory where you want to put your
     local copy the CVS HTML tree. For example:
 
         mkdir ~/project/www
@@ -19,7 +25,7 @@
         export CVS_RSH=ssh
         cvs -z3 -d:ext:address@hidden:/web/projectname co projectname
 
-5.  Then, in the dir \~/project/www/projectname, you should copy all the
+5.  Then, in the directory \~/project/www/projectname, copy all the
     files you want to insert in the CVS HTML tree. For example:
 
         cp ~/tmp/index.html ~/project/www/projectname
@@ -30,22 +36,32 @@
         cd ~/project/www/projectname
         cvs add index.html
         cvs add mydir
-        (or: cvs add index.html mydir)
+        # (or: cvs add index.html mydir)
         cvs commit
 
 Done! The webpages will be updated within an hour. The location of your
-homepage is the default URL in your project's Active Features.
+homepage is the default URL in your project's Select[ed] Features.
 
-Unlike source repositories, the web repository must always use CVS. This
-is due to the complex process involved with getting the files ultimately
-onto the real www.gnu.org machine, and supporting multiple VC's is not,
-at present, practical.
+Similarly, updating your web pages after the initial import is a matter
+of updating and committing in your CVS tree.
 
-If you would like further information, you may be interested in:
+Exception: large updates, involving either many updates or many
+megabytes, may not be fully completed.  Unfortunately, there is no
+warning when this happens (Savannah does not receive any information
+from the backend FSF machines), it's just that some files may not be
+present.  If you notice this, the thing to do is submit a new ticket at
+<https://savannah.gnu.org/support/?group=administration>.
 
-> -   reading
->     <http://www.freenix.org/unix/linux/HOWTO-vo/CVS-RCS-HOWTO.html>
-> -   executing info cvs to get more information
-> -   reading the Quick reference to CVS at
->     <http://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_17.html>
->     (node "Invoking CVS" in the info file).
+For Savannah administrators
+---------------------------
+When a project's web pages, we can retrigger the update at the FSF side
+with the same command that is run by the CVS loginfo hook
+([[SavannahInternals]]).  Do this on the vcs machine (though probably it
+does not technically matter).
+
+    # T=gnu or T=nongnu
+    # PROJ=project identifier
+    vcs$ curl http://www.gnu.org/new-savannah-project/new.py \
+              -s -F type=$T -F project=$PROJ
+
+It may take more than one call, a few minutes apart.