* -d to daemonize, -D to daemonize with specifying

[citadel.git] / webcit / README.txt

diff --git a/webcit/README.txt b/webcit/README.txt
index fa3df2b82f9a71cd536f0f1bd6958ccc810d6c2e..20b9ef8cd24eccf336dd7e441c11e2800abb3099 100644 (file)
--- a/webcit/README.txt
+++ b/webcit/README.txt
@@ -1,5 +1,5 @@
                         WEBCIT for the Citadel System
-                               version 6.84
+                               version 7.02
  
    Copyright (C) 1996-2006 by the authors.  Portions written by:
        Art Cancro
@@ -33,7 +33,6 @@
    [http://cerca.html.it/cgi-bin/cerca.cgi?q=nifty+corners].  This component
    is licensed to you under the terms of the GNU General Public License.
 
-
    The Citadel logo was designed by Lisa Aurigemma.
 
  
@@ -57,11 +56,11 @@ to be attractive and easy to navigate.
  Unline some web-based packages, WebCit contains its own standalone HTTP
 engine.  As a result, you can get it running quickly without all that tedious
 mucking about with Apache configuration files and directories.  WebCit is not
-intended to replace your Apache server, however -- it *only* provides a front
-end to Citadel.  If you do not have another web server running, you may run
-WebCit on port 80; however, in the more likely situation that you have Apache
-or some other web server listening on port 80, you must run WebCit on another
-port.  The default is port 2000.
+intended to be a general-purpose web server, however -- it *only* provides a
+front end to Citadel.  If you do not have another web server running, you may
+run WebCit on port 80; however, if you have Apache or some other web server
+listening on port 80, you must run WebCit on another port.  If you do not
+specify a port number, WebCit will bind to port 2000.
  
  To compile from source, enter the usual commands:
   ./configure --prefix=/usr/local/webcit   [or whatever directory you prefer]
@@ -78,6 +77,10 @@ port.  The default is port 2000.
  After running setup, you just point your web browser to whatever port you
 specified, such as:
  
+  http://your.host.name
+ 
+ (or if you specified some other port, such as 2000 in this example...)
+ 
   http://your.host.name:2000
  
  ...and log in.
@@ -109,13 +112,15 @@ the "webserver" program:
      You can leave this out, in which case WebCit will listen on all
      available network interfaces.  Normally this will be the case, but if
      you are running multiple Citadel systems on one host, it can be useful.
+     You can also use this option to run Apache and WebCit on different IP
+     addresses instead of different ports, if you have them available.
  
   -> http_port: the TCP port on which you wish your WebCit server to run.  If
      you are installing WebCit on a dedicated server, you can use the
      standard port 80.  Otherwise, if port 80 is already occupied by some
      other web service (probably Apache), then you'll need to select a
      different port.  If you do not specify a port number, WebCit will attempt
-     to use port 2000.
+     to use port 80.
      
   -> tracefile: where you want WebCit to log to.  This can be a file, a
      virtual console, or /dev/null to suppress logging altogether.
@@ -176,7 +181,7 @@ the static/ directory.  WebCit will properly serve it from there.
  ----------------
  
  WebCit contains support for calendaring and scheduling.  In order to use it
-you must have libical v0.24 (or newer) on your system.  You must also be
+you must have libical v0.26 (or newer) on your system.  You must also be
 running a Citadel server with calendaring support.  The calendar service will
 be automatically configured and installed if your host system supports it.
  
@@ -295,6 +300,6 @@ that may differ in design but use the same TinyMCE (which is the default that We
  
  That's all you need to know to get started.  If you have any questions or
 comments, please visit UNCENSORED! BBS, the home of Citadel, at
-uncensored.citadel.org.
+http://uncensored.citadel.org - and go to the "Citadel Support" room.