The Lab pre-provisions a stub website and course calendar for every course offered in a give quarter. Please look below for information on how find, access and modify these websites.
How are Course Webs named?
We have naming scheme for a standard directory hierarchy to contain course web data. This naming scheme is reflected in both the filesystem path and url for each course.
The first element of the path is the course number, examples: cse143, cse333, csep512
The second element is the quarter in which the course is given. This is a 2 digit year, followed by a 2 letter quarter abbreviation. The quarter paths for 2017 would be: 17wi, 17sp, 17su, 17au
See below on how these elements are used in the URL and filesystem spaces
What is the URL for my course web?
Course URLs look like this:
How do I get to the docroot?
You can access the docroot for your courseweb from any CSE managed host.
From a unix system you can find the files in the cse file tree at:
From a Windows host your O: drive should already be mapped, so files can be located at:
What if I want to host my course web somewhere else?
You can use a meta-refresh element in your index.html file as follows:
<html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>YOUR COURSE NAME</title> <meta http-equiv="refresh" content="0;URL='https://URL OF NEW DESTINATION'" /> </head> <body> <p>This page has moved to a <a href="https://URL OF NEW DESTINATION'"> https://URL OF NEW DESTINATION/</a>.</p> </body> </html>
Do my TA's have access to modify course web files too?
Yes! They are added to a unix group based on information in the TA database maintained by Pim. If they're listed as a TA for your course, they'll get permissions.
I want to restrict some files to authenticated users only
You'll find directories named 'uwnetid' and 'csenetid' in your course web docroot. Those two directories will force users to authenticate with either their UWNetID or CSENetID respectively. If you want different authentication controls, you can create a directory and place an .htaccess file within, following our the guidelines found in our web authentication guide: https://www.cs.washington.edu/lab/web#authentication.