Please note that the Quick Help will not be fully functional until version 1.0 is actually released.
If you find any errors or inconsistencies in this guide, please let me know so that I can correct them.
*.cfg files, your banner.ad file, your adminpass.cgi file and your data/users file before upgrading. These files contain your configuration settings and user settings. If you overwrite them, you will have to reconfigure your Finger Server and re-add all users... You don't really want to do that. =)
*.cfg files, banner.ad, adminpass.cgi and users file to their proper locations on your web server.
Note: You do not need to copy the directories again, only the files inside the directories.
htdocs directory and only upload those.
unzip (Unix) should have no problem doing this for you.
finger directory, you should have now have two directories, one named cgi-bin and one named htdocs. The cgi-bin directory contains all of the scripts and files that should be uploaded to a cgi-bin directory or any location on the webserver that can execute CGI scripts. The htdocs directory contains all files that should not be placed in a cgi-bin directory. (This is due to the fact that some webservers won't serve html and image content from the cgi-bin directory...)
admin, user and data. These three contain the administration scripts, user scripts and user data respectively.
Note: some zip utilities (such as WinZip) will not extract the data directory from the Unix version of the distribution. If you do not have a data directory, follow these steps:
data inside your cgi-bin directory.
users. Leave it blank and save it in your new data directory.
users file... The full filename should just simply be users.
#!/usr/bin/perl on the first line. If, for example, your server's path to perl was /bin/perl then you would need to change the top line in each file to #!/bin/perl.
The three scripts you need to edit are:
/cgi-bin/finger.cgi
/cgi-bin/admin/admin.cgi
/cgi-bin/user/user.cgi
If you are not sure what your server's path to perl is, you can telnet to your server and issue the command whereis perl or ask your system administrator. Note: /usr/bin/perl is the normal path to perl on unix systems, so you probably won't even have to make these changes.
NOTE: If you are uploading these files to a Unix machine and you have edited these three files, be sure to save these files in the unix text format (LF instead of CR/LF). If you do not do this, your scripts will not work! Windows 95/NT users can find an excellent text editor that will save unix text files properly at www.textpad.com.
finger in your cgi-bin directory and a directory named finger in your html path. Feel free to use any directory name you wish, finger is only an example.
/cgi-bin/finger directory on your webserver.
/finger, on your webserver.
/cgi-bin/finger directory on your web server, create two additional directories. One should be named plans and the other should be named news.
chmod command to do this. (type man chmod for details) In addition, all most all Windows 95/NT FTP clients allow you to change the permissions of files on a remote server. See your FTP client documentation for instructions.
All *.cgi, *.pl and *.pm files in all directories should have their permissions set to 0755.
Exception: /admin/adminpass.cgi should be set to 0777.
All *.cfg files should also be set to 0777.
The users file located in /cgi-bin/finger/data/ should also be set to 0777.
The banner.ad file should be set to 0777.
All directories, including the main /cgi-bin/finger directory should be set to 0777.
All other files not mentioned here should be set to 0777.
SECURITY NOTE: The instructions above set several files and directories on your webserver to read, write and execute for `world'. This means that anyone who has ssh or telnet access to your server could possibly modify files under your finger server directories. It is neccessary to set your permissions in this way, because a web server, by default, is run with the lowest possible permissions and generally does not have write access to a user's web pages or cgi scripts.
That said, the Finger Server stores configuration information and plan information in your cgi-bin directories and must have write access to specific locations. If you know that your web server does have write access to your Finger Server files as user or group, you can turn off the write bit for world by issuing this command:
chmod -R o-w *
Please make sure you are in cgi-bin/finger before issuing this command!
admin.cgi file in your /cgi-bin/finger/admin/ directory.
For example, if you installed the Finger Server in /cgi-bin/finger/, you would point your browser to http://www.yourdomain.com/cgi-bin/finger/admin/admin.cgi
cgi-bin path, etc.
/cgi-bin/finger/plans/ directory. If you only wish to disable a user account, just change the password.
user.cgi file in the /cgi-bin/finger/user/ directory.
For example, if you installed the Finger Server in /cgi-bin/finger/, they would point their browsers to http://www.yourdomain.com/cgi-bin/finger/user/user.cgi to update their plans.
A nice feature of The Finger Server is the ability to display a short list of the latest plan updates on your main web page. You have the choice of displaying the latest updates from all categories, or only the users in the special category.
grablatest.cgi and grabspecial.cgi rely on Server Side Includes (SSI) in order to display the information. A SSI is a tag that the web server parses before the html is ever sent to the browser. This allows the server to do something such as execute a CGI script and insert the the result directly into the web page. SSI tags generally follow the form of
<!--#element attribute="value"-->
Traditionally, HTML pages that contain SSI tags are named *.shtml instead of *.html. Although, they can be named anything the server admin wishes such as *.ssi or *.shtm. This allows the server to distinguish between a page with SSI tags and one without.
In order to use these two scripts, your server should be able parse SSI tags including the exec SSI tag. If you have trouble, or are not sure, please check with your server admin first.
/cgi-gin/finger/ directory on your web server named grablatest.cgi and grabspecial.cgi. Both of these files' permissions should be set to 0755.
The grablatest.cgi script shows the latest updates from all categories and the grabspecial.cgi script only shows the latest updates from the users in the special category.
*.shtml (or whatever your server is configured for). Next, you will need to insert the SSI tag in the exact place you wish the list of updates to appear. If your finger scripts were located in http://www.yourdomain.com/cgi-bin/finger/ you would use one of the following tags:
<!--#exec cgi="/cgi-bin/finger/grablatest.cgi"-->
or
<!--#exec cgi="/cgi-bin/finger/grabspecial.cgi"-->
Replace /cgi-bin/finger/grab*.cgi with the correct path for your setup.
Note: the only space in the above SSI tags are between the words exec and the cgi.
That's it! If you point your browser to the *.shtml page on your web server, you should see the list of plans where you put your SSI tag.
grablatest.cgi and grabspecial.cgi scripts in the Look and Feel section of the Control Panel.
*.shtml page.
In addition to dislaying the list of updates on your home page, an affiliated or hosted web site can now also do the same. The getfingerlist.cgi script will display the latest updates from all categories.
getfingerlist.cgi script depends on system variables from your finger server to run properly. Each time you make a change to the System Setup, a new getfingerlist.cgi script is written to your /cgi-bin/finger/ directory. You will need to go to your System Setup and submit the page, even if you don't make any changes, to write the script for the first time.
Copyright © 1998-2000 Daniel E. Beckham
danbeck@scott.net
http://www.glazed.org/finger/