Date: Sat, 13 Aug 2005 10:18:01 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: basic newb info
Message-ID: <20050813151801.GC16199@katherina.lan.complete.org>
References: <afb85cb40507111446382e89e9@mail.gmail.com>
 <42FCEC9D.5040201@route-add.net> <20050813044356.GH8640@pongonova.net>
 <afb85cb405081222512efb230f@mail.gmail.com>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <afb85cb405081222512efb230f@mail.gmail.com>
User-Agent: Mutt/1.5.9i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Sat, Aug 13, 2005 at 12:51:18AM -0500, sovietassassin@gmail.com wrote:
> i would like as much information on as many options avalible to
> running a gopher server, like example server readable files, embedded

You might take a look at the sample config file and docs for
Pygopherd and Bucktooth.

Pygopherd can grok server files in several different formats --
primarily those originating with UMN gopherd and bucktooth.  UMN
gopherd files normally look like this:

Path=./file.txt
Name=Some Description
Type=1
Host=+
Port=+

This will add an explicit description and type for the file named
file.txt.

You can also add links to other Gopher servers like this:

Path=/
Name=Quux.Org
Type=0
Host=quux.org
Port=+

Or to Web servers:

Path=URL:http://www.complete.org/
Name=Complete.Org
Type=h
Host=+
Port=+

You can create a file named file.abstract that includes an extended
description of a file.  A file named .abstract in a directory will be
displayed at the top of the directory listing.

PyGopherd can also serve up mbox or maildir mailboxes as directories,
with each "file" being a mail message.  Additionally, you can ZIP up
your site (or part of it) and serve up content directly from the ZIP
file.

See the "handler" options.

> options, how things are supposed to work, how to give out/post gopher
> urls -- anything and everything will be put to some kind of use. i

Gopher URLs look like:

gopher://host:port/TYPEurl

So, the Reference page on Quux.org would be:

gopher://quux.org/0/Reference

> just want to learn as much as i can on how it works, why, and how to
> best impliment it. currently ive got a basic gopherd up and running, i
> want to maximize its potential! :)

Hope this helps.  Let me know if you need other info.

-- John

> 
> --jamie
> 
> On 8/12/05, Brian <brian@pongonova.net> wrote:
> > On Fri, Aug 12, 2005 at 08:38:21PM +0200, Alessandro Selli wrote:
> > > sovietassassin@gmail.com wrote:
> > > > could i get some guides or some information on how to layout my gophe=
> r
> > > > system, or files rather. the daemon is up n running and workin just
> > > > fine but with regards to files there are alot that are like .menu or
> > > > something like that. forgive my ignorance but my memory isnt working
> > > > right, but there are alot of things i can do with layouts or
> > > > descriptions or something. so any kind of beginner info for laying ou=
> t
> > > > the system would be appreciated :)
> >=20
> > I've sort of been waiting quietly in the ranks for something
> > similar...John did e-mail me with a couple of example starter files,
> > but maybe I was hoping for a groundswell of examples :)
> >=20
> >   --Brian
> >=20
> >=20
> >
> 
> 
> 

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715