| Question: | I would like to restrict a web page so just my class can get in and see the contents. |
| Answer: |
The easiest way to do want you want is to make a separate
directory in class www.udel.edu server directory.
This way you can have a publicly available class page and a
private page just for currently enrolled students.
There are two ways you or any user on copland can potentially get to the
pages in this directory (1) over the web or (2) from their copland account.
For example, if you class directory name is ENG101 and your
private directory name is spring98, then
you can get to it using any web browser and
the
Once the directory is created, using the mkdir Unix command, you must do several things to safely restrict it to just your class.
|
index.html is the special name used for the
main html file which your students will see when they enter your private
web page. As the name implies, this usually has links to the
various parts of your web page.
Here are the commands to set up the index.html.
Issue these commands from inside the spring98 directory.
(Use the cd command to
change to this directory if you are not already in it.)
index.html
index.html
file to allow "all read" and "group write".
| New Files |
This is all you need to get going. You should
start by putting something interesting in the index.html
file. This can point to graphics and other html files, which need
to be added to the directory. This file may also contain a frameset
if you are using frames.
If you need graphics, you can create
the graphics anyplace you like, and then use ftp to
transfer the graphics files to this location.
The graphics and new html files should be tested before they are added to
the index.html file.
You can test them by typing the full location name in the Netscape
"location" window. Once they are tested they can be added to
the common Whatever method you use to put files in the directory, check to make sure your files are readable to all, so your students can see the files with a Web browser. You can set the permissions on all files in your directory with the one command: chmod a+rX your class directory/* to correct the permission modes. This command just needs to be done if you have new files, since the Netscape publishing does not change the permission modes on existing files. |
|---|---|
| Changing Files | With this set up each user can create, rename and modify any file in the group directory. It is easy to destroy some other member's work, so be careful. If two members simultaneously download the same file to their PC for editing then one will be surprised to see their modifications lost when the older modified version is loaded by the other member. This should not be too much of a problem if all changes to common files are are kept short, and longer changes are put in separate files that only one member is working on. In the worst case, you may need to make your changes again. |
| New directories | If you want to add a subdirectory to organize your information even further. This is done with the Unix mkdir command just as above. The directories should be executeable and setgroup bit set. The Unix command for correct directory permission modes is: chmod a+rX directory name |