How to Put Pages in the Production SLAC Web

SLAC 15 Dec 1995


This document is aimed at people wishing to install production Web pages on the SLAC WWW server. Production pages are ones that are at least moderately polished to be shared across groups for some at least moderately long time. In addition to this document, you should also look at SLAC WWW Resources and its subsidiary pages and the SLAC AFS Users' Guide.

Creating Your Group's Home Page

Before putting any pages on the Web, consider the implications of making your information potentially available to the world via WWW and AFS. Take a look at the memo " Privacy and Confidentiality Issues in SLAC WWW Information" to learn about many of the issues.

A quick, no-frills way to provide information is to place pre-existing plain-text, Postscript, or even PDF documents in your WWW groupcode directory or its subdirectories. (See the next section for obtaining a groupcode directory.) If the server doesn't find a file called index.html in your groupcode directory, it will display a navigable list of all the files it finds there. For example, here's what's currently in the Accelerator Department's directory.

If, on the other hand, you'd like to give your pages a more Web-like look and feel, create regular Web pages using the HTML formatting language. Usually, you will want to create a main or "home" page for your group:

Setting Up Sub-Directories

First, you must obtain a UNIX account that is privileged for AFS. Get a UNIX account form from the Help Desk in the lobby of the Computer Group Building (Building 50). After you receive the UNIX account, you have to enable it for AFS, at least partially. See the SLAC AFS Users' Guide, especially the Introduction, for instructions.

Then you need to send email to to obtain production AFS WWW disk space for your group's pages. The space will be usually be named /afs/slac/www/grp/groupcode where the last part, groupcode, is your group's code, e.g., ad.

You should let www-admin know who should be authorized to write into this and any sub-directories your group establishes and who should be able to control that list. For backup, provide at least two usernames. If you expect to install files that total more than 6 Megabytes, let www-admin know that, too, for space planning purposes.

Someone in www-admin will setup two AFS privilege groups and their initial membership and associate them with your space via its Access Control List (ACL). These groups are g-www:g-groupcode and g-www:owner-g-groupcode, where g-www:g-groupcode is the AFS group of usernames that may write into your group's directory(ies) and g-www:owner-g-groupcode is the AFS group of usernames that may change the names in g-www:g-groupcode.

From your group's directory, use the fs listacl command to see what groups are in your ACL. Use the pts member groupcode command to see who's in a particular AFS group in your ACL, e.g., pts member g-www:g-ad. To learn more about AFS, check out the SLAC "Introduction to AFS."

Once your group's directory is set up, login to the SLAC UNIX system and put your home page and the other documents you choose into this Web directory. Or you may create sub-directories and put documents there.

Use the mkdir command to create the sub-directories. For example, to create a new sub-directory addo for group ad:

	cd /afs/slac/www/grp/ad
	mkdir addo
        ls -l

If you want WWW access to the documents to be restricted only to those logged in to the SLAC domain (actually IP number 134.79), put the files in a subdirectory named slaconly. But see AFS Considerations below.

Your group's home page can now be accessed with the URL address,, where homepage is usually groupcode, home, or index.

To understand more about the naming conventions and other aspects of WWW space at SLAC, read the document, " Revised WWW URL and File Naming Scheme".

AFS Considerations

Your Web pages are visible not only through the Web, but also through the AFS file system.

By default, your AFS directory at SLAC and any of its sub-directories are set up so that (a) anyone at SLAC and (b) anyone in the world who is authenticated to AFS within the SLAC cell can:

through just a simple ls /afs/, cat, or other system command.

This means that by default the files are not readable by anyone in the world with AFS privileges.

N.B.: Files restricted in WWW to people logged on to a host in the SLAC domain (actually to an IP address beginning with 134.79) via a slaconly sub-directory are readable, not only to anyone at SLAC, but also to anyone in the world authenticated to the SLAC AFS cell. The files may even be displayed through Web browsers by using a :file (rather than :http) URL.

Referring to Your Group's Production Web Pages

When providing links to your group's Web pages (or pictures, Postscript files, etc.), refer to the files in terms of how the server may find them. Generally, this means using relative addressing, that is, relative URL, which is usually more robust over time than fully qualified URL--and shorter. Fully qualified URL contains the domain name and may have more of the path name.

To specify the URL for your group directory, /afs/, use /grp/groupcode. For example, if you want to provide a link to the file /afs/, use /grp/ad/AD.html for the URL. If you want to link to another file in the same directory as, say, your group's home page, use a format like another-page.html substituting your specific file name.

For more information on relative URL, check out the source for a page like "SLAC WWW Resources." Or take a look at the Internet standards document, RFC 1808.

Creating Web Pages Elsewhere and Transferring Them to UNIX

You may create your Web pages on a non-UNIX platform such as a Macintosh and then transfer them to UNIX to be served by SLAC's WWW server.

Other Places in UNIX for SLAC Web Pages

Sometimes you may create production pages of "publication" quality for a broad spectrum of the SLAC community. These may be appropriate for installation in SLAC's "functional" production Web space. See "Revised WWW URL and File Naming Scheme," especially Guidelines.

At the other end of the spectrum, you may also create pages of interest to yourself and a few colleagues. If you work on UNIX and especially if these are test versions or transient pages, you should put them in a sub-directory named public_html under your home directory.

The original version of this page was adapted in May, 1995, from the Stanford University page, "Instructions for Classes," on how to set up home pages for classes.

Joan Winters, Les Cottrell