In the grand tradition of a certain software company based in Redmond, Washington with a name that belies both its size and its business practices, I have given this project the most descriptive and least exciting name I could think of. It is, in fact, a database system for churches. It keeps track of church records and attempts to make life a little easier for those who can or must work with that data.
There is quite a bit of documentation in the form of explanatory helps, built into the program's interface. However, I don't have much yet to help get it installed. Sorry. If you send me some documentation, I'll make it available.
This is a guess. I haven't installed it yet. Get the release package you want from http://releases.christfor.us, and (assuming Python is installed), run "easy_install PACKAGE_FILENAME". You may have to modify the "easy_install" part to specify that you want to use Python 2.4. On my system it's "easy_install-2.4".
You can also obtain the directory tree using the gitweb interface mentioned below. I recommend it. Once you have the directory tree, I'm not sure what you'd do next. You'll still need to get proper versions of SQLAlchemy and such installed. Maybe I'll post versions of dependencies here later if I have the time. Maybe I'll also provide better instructions for using the gitweb interface. With the directory tree, you can generate your own distribution archives.
Remember to install your RDMBS and create a database in it for use by the Church Database application. Then, you'll need to modify the file default.cfg in the Church Database distribution so that the application knows how to connect to your database system. There's some documentation in that file already, with sample configurations. This is a guess, but the next step should be to have the application create the needed tables by running "tg-admin sql create" from your command line. (That might be done automatically at some point, though.) Once those tables are created, you should be able to start the application by running "start-chdb.py".
Obviously, all of this is untested. I'm currently running the application in development mode on three sites, and it works fine. I just haven't tried installing it into a production site.
Assuming it's all installed, and your RDBMS has the proper tables and such, and you've gotten the Church Database server running, you can then open a web browser at the address "http://127.0.0.1:8080" or possibly "http://localhost:8080". The rest should be self-explanatory.
I haven't spent much time on network security issues, so please configure your firewall so that anything coming from the Internet does not reach port 8080 (or whatever port you're using for Church Database).
Help is welcome. Bug reports (though I don't promise to be extremely fast in responding), documentation, suggestions for better ways to do things, and patches for the source code are all good. If you write something you'd like to incorporate into the code, please consider using git. You can use the gitweb interface to checkout a repository for your own work. Then, if you can make your changes available in an online git repository, I can use git to pull them directly from you. Otherwise, you can also send me those changes in a patch via email. (Remove the spaces and punctuation from j mat jac AT g @ mail. DOT com, then replace the capitalized words with their punctuation equivalent.)