]>
Commit | Line | Data |
---|---|---|
9af9ec33 EW |
1 | /* praxis: services for TSora IRC networks. |
2 | * README: General documentation | |
3 | * | |
4 | * Copyright (c) 2004 Eric Will <rakaur@malkier.net> | |
5 | * Copyright (c) 2003-2004 praxis development team. | |
6 | * | |
7 | * $Id$ | |
8 | */ | |
9 | ||
10 | praxis -- a set of services for TSora networks | |
11 | ============================================== | |
12 | ||
13 | This program is free but copyrighted software; see doc/license for details. | |
14 | ||
15 | Information about praxis may be found at http://praxis.malkier.net/. | |
16 | ||
17 | TABLE OF CONTENTS | |
18 | ----------------- | |
19 | 1. Credits | |
20 | 2. Presentation | |
21 | 3. Installation | |
22 | 4. Command line options | |
23 | 5. Contact and mailing list | |
24 | ||
25 | 1. CREDITS | |
26 | ---------- | |
27 | ||
28 | While praxis isn't directly based on any other program it borrows a decent | |
29 | amount of code from ircd-ratbox and Sentinel2. | |
30 | ||
31 | Information about ircd-ratbox can be found at http://www.ircd-ratbox.org/. | |
32 | Information about Sentinel2 can be found at http://ircd.botbay.net/sentinel/. | |
33 | ||
34 | Currently praxis is largely written by me: | |
35 | rakaur, Eric Will <rakaur@malkier.net> | |
36 | ||
37 | Thanks to testers, contributors, etc: | |
38 | Hwy, W. Campbell <wcampbel@botbay.net> | |
39 | madragoran, Mike Campbell <madragoran@avendesora.net> | |
40 | nenolod, William Pitcock <nenolod@nenolod.net> | |
41 | rintaun, Matt Lanigan <rintaun@projectxero.net> | |
42 | sycobuny, Stephen Belcher <sycobuny@malkier.net> | |
43 | ||
44 | Special thanks to: | |
45 | Hwy, for your continued patience while I badger you endlessly. | |
46 | rintaun, for the SQLite database work. | |
47 | sycobuny, for your continued not-killing-me while I badger your code. | |
48 | tanka, for the book I will someday repay you for. | |
49 | ||
50 | Files that I didn't write most of: | |
51 | src/balloc.c, this was stolen from ircd-ratbox and modified. | |
52 | src/configparse.c, this was stolen from from csircd and modified. | |
53 | src/dlink.c, this was stolen from ircd-ratbox and modified. | |
54 | src/event.c, idea from Hwy, mostly written by me. | |
55 | src/hash.c, this was stolen from ircd-ratbox and modified. | |
56 | src/io.c, this was originally based on Hwy's code. | |
57 | src/match.c, this was stolen from Sentinel2 (from IRCnet ircd). | |
58 | src/net.c, this was originally based on Hwy's code. | |
59 | src/send.c, this was originally based on Hwy's code. | |
60 | src/timer.c, this was stolen from ircd-ratbox. | |
61 | ||
62 | 2. PRESENTATION | |
63 | --------------- | |
64 | ||
65 | praxis is a set of services for TSora-based IRC networks that allows users to | |
66 | manage their channels in a secure and efficient way and allows operators to | |
67 | manage various things about their networks. | |
68 | ||
69 | praxis currently works with: | |
70 | ircd-ratbox 1.x and 2.x in TS5/TS6 | |
71 | ircd-hybrid 7.0 or later in TS5/TS6 | |
72 | ircd-hybrid 6.0 or later in TS3/TS5 | |
73 | csircd 1.4 or later in TS3/TS5 | |
74 | ||
75 | praxis may *possibly* work with other TSora IRCd's running at least TS3. | |
76 | ||
77 | praxis is closer to being based on ircd than it is on Andrew Church's | |
78 | IRCServices. Anope/Epona, Cygnus, OperStats, Auspice, etc are all based on | |
79 | IRCServices and as such have very old legacy code that none of them, except | |
80 | Church, understands. praxis was written completely from scratch with the more | |
81 | complex pieces people usually take from IRCServices being taken from the most | |
82 | modern and actively developed ircd today: ircd-ratbox. | |
83 | ||
84 | 3. INSTALLATION | |
85 | --------------- | |
86 | ||
87 | See the INSTALL file. | |
88 | ||
89 | 4. COMMAND LINE OPTIONS | |
90 | ----------------------- | |
91 | ||
92 | Normally, praxis can be run simply by invoking the "praxis" executable. praxis | |
93 | will then use the defaults specified in the configuraiton file and connect | |
94 | to the specified uplink server. Alternatively, any of the following | |
95 | command-line options can be specified to change the default behavior: | |
96 | -c </path/to/file> - specify the configuration file | |
97 | -d <1|2|3> - start in debugging mode | |
98 | -h - print the help message and exit | |
99 | -n - do not fork into the background | |
100 | -v - print the version information and exit | |
101 | ||
102 | praxis also handles the following signals: | |
103 | HUP - force a REHASH | |
104 | TERM - force a SHUTDOWN | |
105 | USR2 - force a RESTART | |
106 | ||
107 | Upon starting, praxis will parse its command-line arguments, open its log file, | |
108 | parse its configuration file, load its database, connect to the uplink, | |
109 | and (assuming -n is not specified) detach into the background. If praxis | |
110 | encounters an error while parsing the configuration or database files it will | |
111 | terminate immediately. Otherwise, it will run until killed or otherwise stopped. | |
112 | ||
113 | 5. CONTACT AND MAILING LIST | |
114 | --------------------------- | |
115 | ||
116 | Okay, here's the deal. We enjoy coding this program, and we do it for free. You | |
117 | didn't pay anything for this, did you? No. Our time and our effort went into | |
118 | making this program, and now you want us to help you with it, too. Well, that's | |
119 | fine, but do us a favor: READ THE DOCS. Unlike many other programs we've | |
120 | included some fairly extensive documentation. The configuration file itself has | |
121 | a description of every option as well as examples of: how it's used, what it | |
122 | does, and what happens if you turn it on or off. *Please* don't waste our time | |
123 | by asking asinine questions which are clearly answered in the documentation. | |
124 | You'll just make us regret making this program so easy to use that it requires | |
125 | zero intelligence. | |
126 | ||
127 | That said, if you've skimmed the docs and can't find your answer feel free to | |
128 | ask. I've been unable to find the answer I was looking for in many programs | |
129 | myself so I don't mind. Just don't ask us to set it up for you. It's too easy. | |
130 | ||
131 | For announcements and discussions about praxis, subscribe to the mailing list | |
132 | by sending a blank email to praxis-subscribe@lists.malkier.net. | |
133 | ||
134 | For bug reports, please use these forums: | |
135 | http://praxis.malkier.net/modules.php?name=Forums&file=viewforum&f=3. | |
136 | ||
137 | If you're reporting a bug, here's some advice. Be sure to include information | |
138 | on how to reproduce the problem. If you can't reproduce it, you're likely out | |
139 | of luck. You can go ahead and report the problem but chances are if we can't | |
140 | find the cause then we can't fix it. If praxis crashed (with a core file) be | |
141 | sure to include a backtrace for us. You can do this by running something along | |
142 | the lines of "gdb bin/praxis praxis.core" and typing "bt" at the "(gdb)" | |
143 | prompt. If you do all of these things and still manage to keep your report | |
144 | short and concise you will be loved. | |
145 | ||
146 | For patches/modifications to the source code that you would like to share or | |
147 | otherwise comment on, please use these forums: | |
148 | http://praxis.malkier.net/modules.php?name=Forums&file=viewforum&f=2. | |
149 | ||
150 | For general discussion and/or support, please use these forums: | |
151 | http://praxis.malkier.net/modules.php?name=Forums&file=viewforum&f=1. | |
152 | ||
153 | If your problem requires extensive debugging in a real-time situation we may | |
154 | ask that you find us on IRC: | |
155 | rakaur @ #praxis on irc.malkier.net | |
156 | sycobuny @ #praxis on irc.malkier.net | |
157 | rintaun @ #praxis on irc.malkier.net | |
158 | ||
159 | If you've read this far, congratulations. You are among the few elite people | |
160 | that actually read documentation. Thank you. |