Project webpages - Revision history

Gray at 16:57, 20 March 2014

2014-03-20T16:57:03Z

Gray at 16:56, 20 March 2014

2014-03-20T16:56:02Z

Gray: /* The .checkoutrc file */

2014-03-17T07:46:06Z

The .checkoutrc file

Gray at 07:45, 17 March 2014

2014-03-17T07:45:35Z

Gray at 07:44, 17 March 2014

2014-03-17T07:44:44Z

Gray at 23:28, 14 March 2014

2014-03-14T23:28:22Z

Gray at 23:12, 14 March 2014

2014-03-14T23:12:15Z

Gray at 23:11, 14 March 2014

2014-03-14T23:11:18Z

Gray at 23:07, 14 March 2014

2014-03-14T23:07:38Z

Gray at 18:17, 14 March 2014

2014-03-14T18:17:23Z

@@ Line 1: / Line 1: @@
-Each project hosted on Puszcza is assigned a web space available at the following URL:
+Each project hosted on Puszcza is assigned a web space available from the following URL:
   <nowiki>http://www.gnu.org.ua/software/</nowiki>''project''.
 In this example as well as in the discussion below, ''project'' stands for the actual UNIX name of your project.
 __FORCETOC__
 ==Initial import==

← Older revision		Revision as of 16:56, 20 March 2014
Line 4:		Line 4:
	In this example as well as in the discussion below, ''project'' stands for the actual UNIX name of your project.		In this example as well as in the discussion below, ''project'' stands for the actual UNIX name of your project.

		+	__FORCETOC__
	==Initial import==		==Initial import==

@@ Line 47: / Line 47: @@
 ;chmod ''mode'' ''file'' [''file''...]
-Change mode of the listed files to ''mode'', which must be an  octal number.   Shell  wildcards are allowed in file arguments.  After expandind, each file argument must refer to a file in  the  current directory or one of its subdirectories.
+Change mode of the listed files to ''mode'', which must be an  octal number.   Shell  wildcards are allowed in file arguments.  After expanding, each file argument must refer to a file in  the  current directory or one of its subdirectories.
 The following statements cause creation of a <tt>.htaccess</tt> file. It is created in the same directory as the '''.checkoutrc''' file being processed.

@@ Line 47: / Line 47: @@
 ;chmod ''mode'' ''file'' [''file''...]
-Change mode of the listed files to mode, which must be an  octal number.   Shell  wildcards are allowed in file arguments.  After expandind, each file argument must refer to a file in  the  current directory or one of its subdirectories.
+Change mode of the listed files to ''mode'', which must be an  octal number.   Shell  wildcards are allowed in file arguments.  After expandind, each file argument must refer to a file in  the  current directory or one of its subdirectories.
 The following statements cause creation of a <tt>.htaccess</tt> file. It is created in the same directory as the '''.checkoutrc''' file being processed.

@@ Line 38: / Line 38: @@
 When parsing a '''.checkoutrc''' file, empty lines and lines beginning with a '''#''' sign are ignored. Generally speaking, the '''#''' sign introduces a comment, unless it appears within a quoted string or is escaped using the backslash character.  All material starting at that sign and up to the end of the line is ignored.
-Each non-emtpy line from a '''.checkoutrc''' is split into words using algorithm similar to the one used by Bourne shell.  The first word is a ''command verb'' and the rest of words are its arguments. Command verbs are case-insensitive. Available verbs are:
+Each non-emtpy line from a '''.checkoutrc''' is split into words using algorithm similar to the one used by Bourne shell.  The first word is a ''command verb'' and the rest of words are its arguments. Command verbs are case-insensitive. Available commands are:
 ;link ''src'' ''dst''

@@ Line 4: / Line 4: @@
 In this example as well as in the discussion below, ''project'' stands for the actual UNIX name of your project.
-== Initial import ==
+==Initial import==
 To populate the webspace with the actual content, it must be checked in to the CVS repository <nowiki>cvs.gnu.org.ua/webcvs/</nowiki>''project''/''project''. The recommended way to do so, is described below.
@@ Line 27: / Line 27: @@
 Another way to do initial import is to check out the empty repository first (using the command above), populate it with the files, run <tt>cvs add</tt> and commit the changes using <tt>cvs commit</tt>.
-== Updates ==
+==Updates==
 Whatever method you use for initial import, you will end up with your content available via http and a local copy of the working tree.  If you wish to modify the content later, do the necessary changes to your local copy and commit them.  Use <tt>cvs add</tt> to add a file or directory. Use <tt>cvs update -P</tt> before you commit a file, and <tt>cvs commit </tt> to perform the commit. Committed changes become visible on www.gnu.org.ua within 2 seconds after the commit. For further details on <tt>cvs</tt>, such as reverting to a previous version, or getting a diff output of particular changes, see the [http://cvs.nongnu.org CVS documentation].
-== The .checkoutrc file ==
+==The .checkoutrc file==
 Due to security reasons, any <tt>.htaccess</tt> files are removed during synchronization.  However, special provisions are made to allow you to control the way <tt>httpd</tt> handles your files. Special files named '''.checkoutrc''' can be included in the commit.  When encountered, such files are treated as lists of commands to be performed after

← Older revision		Revision as of 23:11, 14 March 2014
Line 53:		Line 53:
	;xbithack ''on''\|''off''		;xbithack ''on''\|''off''
	:If set to ''on'', enables the Apache ''XBitHack''.		:If set to ''on'', enables the Apache ''XBitHack''.
		+	;ssi ''on''\|''off''
		+	If set to ''on'', enables server-side includes, by adding the following statement to the <tt>.htaccess</tt> file:
		+	AddHandler server-parsed .html
		+
		+	The following statements are reproduced in <tt>.htaccess</tt> verbatim:
		+
		+	; redirect ''args''...
		+	; rewritebase ''args''...
		+	; rewritecond ''args''...
		+	; rewriteengine ''args''...
		+	; rewritemap ''args''...
		+	; rewriteoptions ''args''...
		+	; rewriterule ''args''...

← Older revision		Revision as of 18:17, 14 March 2014
Line 26:		Line 26:

	Whatever method you use for initial import, you will end up with your content available via http and a local copy of the working tree. If you wish to modify the content later, do the necessary changes to your local copy, schedule them for commit and run <tt>cvs commit</tt>. The changes will become available within 2 seconds after the commit finishes.		Whatever method you use for initial import, you will end up with your content available via http and a local copy of the working tree. If you wish to modify the content later, do the necessary changes to your local copy, schedule them for commit and run <tt>cvs commit</tt>. The changes will become available within 2 seconds after the commit finishes.
		+
		+	Notice that due to security reasons, any <tt>.htaccess</tt> files are removed during the synchronization. However, special provisions are made to allow you to control the way <tt>httpd</tt> handles your files.
		+
		+	== The .checkoutrc file ==
		+
		+	To be continued...