UGO
ABOUT
With ugo you can show a summary of the last "X" files
(where X is a number you choose) in a specific directory in
your gopher hole, sorted chronologically (the last file
created will be the first, and so on). It will show only
the fisrt paragraph of your files and will use as title
their last modification date.[1]
You could find ugo useful if you want to have a gopher
log ("glog", "phlog", or whatever).
It's possible to find an example of its output here:
(DIR) chr's log
Note: All the scripts present here are "beta". That means
that they probably won't work as expected. I've been using
them and they've been working fine, but things could
probably change.
Note: The files are compressed with "zip". After you
download a file (e.g., "snarf FILE.zip"), you'll have to
decompress it (that is, "unzip FILE.zip") and, if the file
is "download-ugo.sh" or "ugo.sh", make it user executable
(e.g., "chmod u+x FILE.sh").
FOR THE IMPATIENT
You can download this script:
(BIN) download-ugo.sh.zip
make it executable (chmod u+x download-ugo.sh) and run
it. It will download ugo and co., create all the needed
stuff and write a first post. Then, you can visit:
gopher://sdf.lonestar.org/1/users/YOUR-USER-NAME/log/
and view your log! Otherwise, you can read more info
below.
INSTALLATION
It's a shell script, so you have to download it:
(BIN) ugo.sh.zip
make it user executable and run it it wherever you like.
You'll need to specify a directory with the variable
$LOG_DIRECTORY, relative to your gopher directory,[2]
where you'll write your posts (by default it will read
.txt file, but you can change the extension).
OPTIONS
The script uses a configuration file, ".ugorc", that will
be placed in $LOG_DIRECTORY (not in your $HOME). All
variables that involve files are relative to
$LOG_DIRECTORY.
If you want a "banner" (header) specify its location in
the variable $LOG_BANNER.
You can use "comment.cgi" if you want to allow comments to
your posts:
(BIN) comments.cgi.zip
The option is enabled by default. With it, the script will
generate auxiliary files for every file in the frontpage,
with extension "go" (can be changed in .ugorc) that will
be like gophermaps. That is, you will have your original
"mypost.txt" and "mypost.txt.go", but the latter will have
a syntax that make it possible to add links. Specifically,
that file is needed to put a link that people can use to
leave a comment to your post. If you enable a "pheed",[2]
specify its location in $PHEED.
It's also possible to have an archive page that will have
links to older files (grouped by year and month) with
their modification time appended.
(BIN) archive.cgi.zip
If you want to use "comment.cgi" and/or "archive.cgi",
you'll have to download the relative file, put it in your
$LOG_DIRECTORY and make it executable by the server
(chmod 750).
If you *don't* want comments or archive, you can leave the
variables $COMM_SCRIPT or $ARCH_SCRIPT (respectively)
blank. The same for $PHEED.
USAGE
ugo.sh [ [FLAG] [FILE.txt] ]
If you run it as "ugo.sh", it will update the gophermap in
$LOG_DIRECTORY. If you run it as "ugo.sh FILE.txt", it
will let you create the file FILE.txt with your $EDITOR
(or $VISUAL or vi) and update the gophermap in
$LOG_DIRECTORY. Finally, if you run it as "ugo FLAG", it
its behaviour will be defined by FLAG. Here's a summary of
FLAGs and what ugo will do:
+-----------------------------------------------------------------+
| FLAG | FUNCTION |
+----------------+------------------------------------------------+
| ls | Show a list of .txt files in $LOG_DIRECTORY |
+----------------|------------------------------------------------+
| mod FILE.txt | Modify a file without changing its modif. time |
+-----------------------------------------------------------------+
More to come...
MISC
Ah.. "ugo" stands for Update GOpher.
[1] The script is quite SDF specific.
[2] For instance, put LOG_DIRECTORY=log if the directory you
want to use is located in /ftp/users/$USER/log
[3] A "pheed" is like a web feed. New comments will appear
there. It's optional, as comments will always appear in
the page they refer. The "pheed" idea is not mine. See
(DIR) georg