Content:CS Dept Site Setup - Revision history

Kay: CS Dept Site Setup moved to Content:CS Dept Site Setup

2009-02-10T16:50:01Z

CS Dept Site Setup moved to Content:CS Dept Site Setup

← Older revision	Revision as of 16:50, 10 February 2009
(No difference)

Kay at 22:38, 1 February 2009

2009-02-01T22:38:49Z

← Older revision		Revision as of 22:38, 1 February 2009
Line 36:		Line 36:

	http://winscp.net/eng/download.php		http://winscp.net/eng/download.php

			=== Changing the News Section ===
			You update the news blog --- just add a new entry and mark it for
			publication when you save it --- and then rebuild the blog. The second
			part is the part that is most easily missed. You have to select rebuild
			from the menu on the left side of the blog page and then something like
			"rebuild all" from the pop-up. There is a cron script that runs every
			five minutes or so which checks to see if the rss file, which will be
			updated when you rebuild the blog, has been modified more recently than
			the html include file and regenerates the html if it has. So there will
			generally be a delay between the rebuild of the blog and the update
			showing up in the web.

			The jobs blog works the same way.

			The cron job is
			:<code>/clients/www/html/cgi-bin/feed2page.pl -f /clients/www/html/cgi-bin/feeds.list</code>

			feeds.list has the format, one per line:

			:<code><filename.rdf>\|<filename.html></code>

			where <filename.rdf> is the pathname of the the rss file and
			<filename.html> is the pathname of the html include file.

Kay: /* Shell Access */

2009-01-30T21:03:56Z

Shell Access

← Older revision		Revision as of 21:03, 30 January 2009
Line 30:		Line 30:
	http://www.putty.org/		http://www.putty.org/

	You don't need to install it: it's entirely a self-contained .exe file.		You don't need to install it: it's entirely a self-contained .exe file. Enter <code>quark.cs.earlham.edu</code> for the hostname. Use your ACL username and password.

	==== Transferring Files ====		==== Transferring Files ====

Kay: /* Staging */

2009-01-28T22:57:58Z

Staging

← Older revision		Revision as of 22:57, 28 January 2009
Line 6:		Line 6:

	The files for the staging site are located on quark at <code>/clients/www/staging/html</code> and <code>/clients/www/staging/cgi-bin</code>.		The files for the staging site are located on quark at <code>/clients/www/staging/html</code> and <code>/clients/www/staging/cgi-bin</code>.

			To access staging from a web browser, go to http://staging.cs.earlham.edu/ You'll be prompted for the group's username and password. If you've forgotten these or haven't gotten them yet, talk to one of the other content group members.

	=== Live ===		=== Live ===

Kay at 18:30, 21 January 2009

2009-01-21T18:30:18Z

@@ Line 14: / Line 14: @@
 from inside the <code>html</code> directory.
-The files for the live website are located on quark at <code>/clients/www/html</code> and <code>/clients/www/html/cgi-bin/.
+The files for the live website are located on quark at <code>/clients/www/html</code> and <code>/clients/www/html/cgi-bin/</code>.
 === Cruft ===
@@ Line 21: / Line 21: @@
 * [[Content CVS Directories]] - a breakdown of the directories and what's in them

Kay at 18:20, 21 January 2009

2009-01-21T18:20:48Z

← Older revision		Revision as of 18:20, 21 January 2009
Line 2:		Line 2:

	=== Staging ===		=== Staging ===
	The staging server can be accessed at staging.cs.earlham.edu. This contains a copy of everything on the website and everything that's currently being worked on. We'll use this as a place to make changes before we commit them to going live. '''Note:''' This is the only place that you should make changes to the ~~pages~~!!		The staging server can be accessed at staging.cs.earlham.edu. This contains a copy of everything on the website and everything that's currently being worked on. We'll use this as a place to make changes before we commit them to going live.
			'''Note:''' This is the only place that you should make changes to the website!!

			The files for the staging site are located on quark at <code>/clients/www/staging/html</code> and <code>/clients/www/staging/cgi-bin</code>.

	=== Live ===		=== Live ===
			After we've reviewed changes to a page or to a project, we can copy them over to the live website by using rsync. This can be either just files or entire directories. Immediately after, commit the changes to the CVS tree by running

			:<code>cvs commit</code>

			from inside the <code>html</code> directory.

			The files for the live website are located on quark at <code>/clients/www/html</code> and <code>/clients/www/html/cgi-bin/.

	== ~~Using CVS~~ ==		=== Cruft ===
	~~''Note:'' When running any CVS commands, you'll need to specify <code>-d /clients/users/cvs</code> to specify which cvsroot you're talking about.~~

	~~Otherwise you can also put~~ a ~~line~~ in ~~your .bashrc file like this:~~ <code>~~export CVSROOT='~~/clients/~~users~~/~~cvs'~~</code> ~~if you're~~ only ~~going to use the one~~ that ~~contains the content~~.		There's a lot of currently unused stuff in <code>/clients/www</code> and also in the <code>html</code> directory. Some of this is currently part of CVS. Eventually we should move over to SVN and only put in there stuff that's actually used.

	* [[Content CVS Directories]] - a breakdown of the directories and what's in them		* [[Content CVS Directories]] - a breakdown of the directories and what's in them

Kay at 18:11, 21 January 2009

2009-01-21T18:11:17Z

← Older revision		Revision as of 18:11, 21 January 2009
Line 1:		Line 1:
	~~== Locations ==~~		Both versions of the department's website run off [[Servers:Quark\|Quark]].
	* The department's website ~~runs~~ off [[Servers:Quark\|Quark]].
	* The live copy is located at <code>/clients/www</code>		=== Staging ===
	** The ~~html itself and the root for the website is located~~ at ~~<code>/clients/www/html</code>~~		The staging server can be accessed at staging.cs.earlham.edu. This contains a copy of everything on the website and everything that's currently being worked on. We'll use this as a place to make changes before we commit them to going live. '''Note:''' This is the only place that you should make changes to the pages!!
	* This ~~is automatically copied over from CVS:~~
	** CVS for the website is ~~located at <code>/clients/users/cvs/html</code>~~		=== Live ===
	** Committing to CVS will automatically cause the changes to ~~be copied to <code>/clients/www/html</code>~~

	== Using CVS ==		== Using CVS ==

Kay at 18:08, 21 January 2009

2009-01-21T18:08:57Z

← Older revision		Revision as of 18:08, 21 January 2009
Line 13:		Line 13:

	* [[Content CVS Directories]] - a breakdown of the directories and what's in them		* [[Content CVS Directories]] - a breakdown of the directories and what's in them
	* [[Brief CVS Tutorial]] - specific to our setup

Kwanous: /* Using CVS */

2009-01-12T20:22:48Z

Using CVS

← Older revision		Revision as of 20:22, 12 January 2009
Line 8:		Line 8:

	== Using CVS ==		== Using CVS ==
	''Note:'' When running any ~~of these~~ commands, you'll need to specify <code>-d /clients/users/cvs</code> to specify which cvsroot you're talking about.		''Note:'' When running any CVS commands, you'll need to specify <code>-d /clients/users/cvs</code> to specify which cvsroot you're talking about.

	Otherwise you can also put a line in your .bashrc file like this: <code>export CVSROOT='/clients/users/cvs'</code>		Otherwise you can also put a line in your .bashrc file like this: <code>export CVSROOT='/clients/users/cvs'</code> if you're only going to use the one that contains the content.

	* [[Content CVS Directories]] - a breakdown of the directories and what's in them		* [[Content CVS Directories]] - a breakdown of the directories and what's in them
	* [[Brief CVS Tutorial]] - specific to our setup		* [[Brief CVS Tutorial]] - specific to our setup

Kwanous: /* Checking Out */

2009-01-12T20:22:11Z

Checking Out

← Older revision		Revision as of 20:22, 12 January 2009
Line 14:		Line 14:
	* [[Content CVS Directories]] - a breakdown of the directories and what's in them		* [[Content CVS Directories]] - a breakdown of the directories and what's in them
	* [[Brief CVS Tutorial]] - specific to our setup		* [[Brief CVS Tutorial]] - specific to our setup

	~~=== Checking Out ===~~
	When you're checking out a part of the branch with CVS, be sure to specify that part. It should always start with 'html' if you're working with the website content. Some of the important directories are here: