Python Community Server
         --> alpha test v0.12
/   \      /  \    -----------
|    O     O   |  / read me   \
|       V      | C   hellooo~  |
\             /   \   hoo hoo /
 / \        / \    -----------
|\  \      /  /|
| \  \    /  / |
|  ^^^    ^^^  |
 \__  ____  __/
    vv    vv

PyCS is still "unstable".  That means it's perfectly suitable to use for your 
weblog community server (it's been running and some others 
quite happily for a fair while now) but it may require some hacking to get it to 
work on your system.

Here are some notes to get you going.  First, you'll want to read the setup howto:

	Medusa -

		The docs are at the above URL, but you want to download the newer
		version from SourceForge:
		Unpack this into a subdirectory of your PyCS directory called
		'medusa'.  When you run 'make install' it will be saved into
	MetaKit -
		Install this as usual.  Put and into your 
		PyCS dir if it doesn't work.


		The PyCS page on the Community Server Wiki has the most up-to-
		date information here.  See also the linked setup HOWTO.
	Virtual Hosting:
		If you already have a copy of Apache running on your box and 
		want PyCS to only serve requests for a certain (virtual) host or 
		group of hosts, you can accomplish this with mod_rewrite and 
		Put the following in your VirtualHost block:
			RewriteEngine On
			RewriteRule ^(.+){HTTP_HOST}$1 [P]
		This way, Apache will send the requested hostname through to the 
		PyCS server, allowing it to work out virtual hosts on its own. 
		See /etc/pycs/rewrite.conf for more info on how to do this.
		Here's a more complete example of a VirtualHost block that 
		proxies requests through to a PyCS server.
		        DocumentRoot /var/www/external
		        ServerAlias *
		        ErrorLog /var/log/apache/rcs-error.log
		        CustomLog /var/log/apache/rcs-access.log combined
		        RewriteEngine On
			RewriteRule ^(.+){HTTP_HOST}$1 [P]
		This tells Apache that requests for and *
		should be sent through to the PyCS using the ~~vhost~~ syntax
		(see rewrite.conf for more info), and that logging should go
		to /var/log/apache/rcs-{error,access}.log.
		You'll want to run PyCS as an unprivileged user.  'make install' 
		will create a www-pycs account for you and put everything in the 
		right places.

		Once you've started the server, run 'ps auxf' and check that 
		/usr/bin/python /var/lib/pycs/bin/ is not running as 
		root.  It should be 'www-pycs' or the user you specified on 

		It writes three log files in /var/log/pycs: access.log, etc.log 
		and error.log. etc.log logs everything written to stdout and 
		error.log logs everything written to stderr, while access.log 
		logs hits and stuff - what you might expect to see from a basic 
		Apache access.log.
		The referrer tracking code writes a log file per blog in the 
		same directory to track the hits in the last 24 hours.  The 
		format here is slightly different; see /system/ and 
		/system/ for more information.


	If anyone wants to fix anything or add features, go ahead!
	BUT: join the mailing list and announce what you're about to do first, 
	so everyone else knows not to work on the same thing.

	Details here:




	Community Servers in general:


	All original code, search integration:
		Phillip Pearson, pp at myelin dot co dot nz (English community server)
	Referrer tracking and hit counting, pretty much everything since late 2002:
		Georg Bauer, gb at murphy dot bofh dot ms (German community server)


		Yasushi Iwata (Japanese community server)
		Michael Hay, Michael dot Hay at hds dot com
	Password changing:
		Scott Lewis, scott at bandwidthcoop dot org