We recommand these steps to publish your web pages on Lamont's official web site. If you want use the design of the lamont web site for your personal/professional web pages or your require more advanced web site contact the Webmaster, or submit a Web Request.

1. Personal Web Pages

These pages are personal/professional web pages that are composed by the user and reside in a folder in the user's home directory (Unix filesystem).

• Step 1. Create your web page on your desktop. There are many easy to use html producers such as Microsoft Word. Name the file index.html
• Step 2. Using any ftp client, such as fetch, create a folder called public_html in your home directory and place your index.html in it (Use ftp/fetch to transfer the files). You can use fetch to create the folder or telnet to a UNIX server and use 'mkdir public_html' command.


• Ftp Host: ftp.ldeo.columbia.edu
• Ftp Username: USERNAME
• Ftp Password: Your Unix (email) password
• (At this point your are in your home directory server disk space, "Home Directory")
• (Transfer the index.html file over to ftp.ldeo.columbia.edu)
  
• Step 3. Connect to your web site at the address:
  
  http://www.ldeo.columbia.edu/~USERNAME
  
• Step 4. Email phone-request@ldeo.columbia.edu to add your web page to phone directory search.

Note: Server side disk space can be obtained upon unavailibility of space and need. Such requests should be made to 'LDEO Web System Manager'. In those cases, after such requests are granted,

• Step 1. Same as above
• Step 2. Using any ftp client, such as fetch, create a folder called ????


• Ftp Host: www.ldeo.columbia.edu
• Ftp Username: USERNAME
• Ftp Password: Your Unix (email) password
• (At this point your are in your home directory server disk space, "Home Directory")
• (At the ftp> prompt type:
  ftp> cd /system/ldeo-web/docs/users/USERNAME
• (Transfer the index.html file over to www.ldeo.columbia.edu)


• Step 3. Connect to your web site at the address:
  
  http://www.ldeo.columbia.edu/users/USERNAME
  
• Step 4. Same as above
  

2. Projects and Facilities Web Pages

In general, these web pages are built on the disk space dedicated to the project or the group and linked directly under one of the existing categories on Lamont's web site. If such disk space is not available to the project, some disk space on the web server can be alloted for the project's web pages. Requests for such space should be send from the project's PI to 'LDEO Web System Manager'.

Server side disk space can be obtained. Such requests should be made to 'LDEO Web System Manager'. In this case, your personal web address would be http://www.ldeo.columbia.edu/users/Project-name

Once the web project's pages are completed, a request should be made to LDEO Web System Manager with the location of the web pages, under which existing category(s) it should be linked, and a short sentence about the project or the facility.

You could also indicate in what section of the main web page your project's web page should be listed under. Provide a title, and a line of summary.

Basically,

A) Do you need a server space? How much? name? Description? If not, point me to your project web page location.
B) Do you want to link it in under any of the existing pages (Reseach, Eductaion, etc.).

HTML Help and Tutorials

http://hotwired.lycos.com/webmonkey/authoring/html_basics/
http://www.ncsa.uiuc.edu/General/Internet/WWW/HTMLPrimer.html

Creating Password Protected Directories

What you are trying to do is called "user authentication". The best place to learn about user authentication is from the source (NCSA). They have a very easy to understand tutorial at the following URL:

http://hoohoo.ncsa.uiuc.edu/docs/tutorials/user.html

Sample .htaccess:

AuthUserFile /the-path/.htpasswd
AuthGroupFile /dev/null
AuthName "Bill's Restaurant"
AuthType Basic

<Limit GET>
require user William
</Limit>

To set up the password for "William" issue the following command:

% /usr/local/bin/htpasswd -m -c /home/directory/[login]/.htpasswd William

Use the htpasswd command without the -c flag to add additional users; e.g.:

% /usr/local/bin/htpasswd /home/directory/[login]/.htpasswd peanuts
% /usr/local/bin/htpasswd /home/directory/[login]/.htpasswd almonds
% /usr/local/bin/htpasswd /home/directory/[login]/.htpasswd walnuts