]> jfr.im git - irc/UndernetIRC/undernet-development-env.git/blame - etc/gnuworld/cservice.conf
Initial import of undernet development env
[irc/UndernetIRC/undernet-development-env.git] / etc / gnuworld / cservice.conf
CommitLineData
446026a1
SW
1# Channel Services configuration file.
2#
3# sql_host = Hostname/IP of the PostgreSQL server.
4
5sql_host = db
6sql_port = 5432
7
8# sql_db = Name of the database.
9# (To create from the template, run cservice.sql through Postgres)
10
11sql_db = cservice
12
13# sql_user is the username to pass to Postgres on connection.
14# Usefull if your account name is not the same as your Database
15# username.
16
17sql_user = cservice
18sql_pass = cservice
19
20# General 'Bot' options.
21
22nickname = X
23username = cservice
24hostname = undernet.org
25userdescription = For help type: /msg X help
26# Important: remove 'd' deaf mode if you intend to enable cservice FLOODPRO
27mode = +idk
28
29#
30# Channel to relay flood/warnings/exceptions, etc.
31#
32
33pending_page_url = http://www.yoursite.com/live/view_app.php
34
35relay_channel = #coder-com
36
37#
38# Channel to relay useful information, but not quite as annoying
39# as the debug_channel ! (a.k.a privileged user relay channel)
40#
41
42priv_relay_channel = #coder-com
43
44#
45# Channel to relay useful debug information that otherwise
46# annoy CS admins. :)
47#
48
49debug_channel = #coder-com
50
51#
52# Coder channel.
53#
54# Channel used to extract levels to display coder access status.
55
56coder_channel = #coder-com
57
58#
59# Frequency in seconds to check the database for updates.
60#
61
62update_interval = 180
63
64#
65# Number of seconds to sample for flooding.
66#
67
68flood_duration = 30
69
70#
71# Input flood rate.
72#
73# Eg: 30, for 30 points amassed within "flood_duration" seconds.
74#
75
76input_flood = 30
77
78#
79# Output flood rate.
80#
81# Eg: 20480 (20k within "flood_duration" seconds).
82#
83
84output_flood = 20480
85
86#
87# Frequency in seconds to sample after clients channel flood
88#
89
90channels_flood_period = 30
91
92#
93# After how many seconds of absence of flood activity should reduce the FLOODNET value
94# Eg. 300 = 5 minutes.
95
96floodpro_relaxtime = 300
97
98#
99# How many not(ic)es will be stored for an offline user
100# 0 is disallowed, 7 will be used
101
102max_notes = 7;
103
104#
105# Minimum duration at which to set a topic in a non idle channel.
106# (Seconds).
107#
108
109topic_duration = 1800
110
111#
112# Duration at which we check for idle user accounts in memory.
113# (Seconds).
114
115expire_interval = 3600
116
117#
118# How long those accounts should have been idle before they are
119# uncached. (Seconds).
120#
121
122cache_interval = 3600
123
124#
125# How often to commit changes to Pending channels.
126# (Seconds).
127
128pending_duration = 180
129
130#
131# How often to notify changes of Pending channels.
132# (Seconds).
133
134pending_notif_duration = 1800
135
136#
137# How often to check if the connection to the backend has
138# fallen over? (Seconds).
139#
140
141connection_check_frequency = 10
142
143#
144# How many times do we try every 'connection_check_frequency' seconds
145# to reconnect before finally giving up and exiting?
146#
147
148connection_retry_total = 5
149
150#
151# How often (in seconds) should we check all channels that have
152# floating-limit set to see if they need a new limit setting?
153#
154# Note: 30 is a good value, try 1min if you have lots of chans
155# and not so much CPU.
156
157limit_check = 30
158
159#
160# How long (In seconds) should we wait before allowing
161# logins after startup. (Incase you're on a busy network
162# with a really large burst and need things to settle down
163# first to ease up load on the Db).
164#
165
166login_delay = 360
167
168
169#
170# What is the period (in seconds) in which we will check to
171# see if someone has sent too many notes, and what do we
172# define "Too Many" as?
173# Ie: You can send 'note_limit' notes in 'note_duration' seconds.
174#
175
176note_duration = 3600
177note_limit = 5
178
179#
180# Pre-cache 'x' days worth of user accounts.
181# This lets you preload all the users who have logged in during the last
182# 'x' number of days to avoid a large number of queries when processing
183# +r accounts during the initial net.burst.
184#
185preload_user_days = 1
186
187#
188# Specify the filename for the 'Admin Log'.
189# Basically a log of all commands admins type.
190#
191admin_logfile = admin.log
192
193#
194# Specify the filename for the 'Command Log'
195# A log of ALL commands issued by ALL users.
196# requires USE_COMMAND_LOG in cservice_config.h
197command_logfile = cs.log
198
199#
200# This option is used only if ALLOW_HELLO is defined in
201# cservice_config.h, thus enabling the HELLO command in cservice.
202# This is the time to block users attempting to flood the bot with
203# hello commands, in seconds.
204#
205hello_block_period = 3600
206
207# Message when login-on-connect (LoC) parameters are incorrect
208# Used with iauthd-c: https://github.com/UndernetIRC/iauthd-c
209#
210loc_message = Insufficient login-on-connect (LoC) parameters - see www.undernet.org/loc/ for help
211
212#
213# What is the period (in seconds) in which we will check for
214# new webrelay messages
215#
216
217webrelay_interval = 10;
218
219#
220# How long the bot should stay in an idle channel before leaving it.
221# This only takes into account join/parts, not privmsg.
222# Default is 2 days (172800 seconds)
223#
224
225part_idle_chan = 172800
226
227#
228# Enable/Disable totp authentication (must be enabled in mod.cservice/cservice_config.h on compliation)
229# 1 = totp enabled, 0 = totp disabled
230
231enable_totp = 0
232
233# A welcome message for a newly accepted channel
234# For empty use '' and it means disabled
235
236welcome_newchan_message = Congratulations! Channel %s has been registered!
237
238# A welcome topic for a newly accepted channel
239# For empty use '' and it means disabled. Applies only on empty channel topic.
240# TOPIC_TRACK must be #define in \include\gnuworld_config.h
241
242welcome_newchan_topic = *** Congratulations! Your channel application has been accepted! ***
243
244# After how much seconds should expire any newly created never logged in user
245
246neverloggedin_users_expiretime = 21600
247
248# Days to expire users
249# 0 = never expire
250
251users_expire_days = 60
252
253# Day length in seconds - refers to users expiration
254
255day_seconds = 86400
256
257# # #
258# *** The Judge settings *** #
259# # #
260
261# Required supporters
262
263required_supporters = 5
264
265# Length of a day in seconds
266
267judge_day_seconds = 3600
268
269# If somebody supports with a 'NO' answer, the channel will be set as noreg
270# for the specified number of days
271
272noreg_days_on_nosupport = 1
273
274# If one of the supporters gets marked as Fraud during channel registration,
275# the channel will be rejected automatically if the value is '1' enabled
276
277reject_app_on_userfraud = 1
278
279# If the value is 1 enabled then all channels at a minimum require an admin to Mark As Reviewed
280# before application can be fully processed by TheJudge
281
282require_review = 1
283
284# If the value is 1 enabled, any channel application with admin comments of objectsions will
285# require manual decision accept/reject by an admin
286
287decide_on_object = 1
288
289# If the value is 1 enabled, after all successful registration stages there will be no automatic accepts.
290# Channel will be left at to 'Ready to review' stage, waiting for an admin's final decision to accept/reject
291
292decide_on_complete = 0
293
294# After how many days will be a channel automatically rejected
295# when it was no decision made by an admin for a 'Ready to review' channel
296
297reviews_expire_time = 100
298
299# After some days, we cleanup the database from old application datas: pending channels, supporters, etc
300# But this applies *only* for Accepted OR Rejected channels!
301
302pendings_expire_time = 30
303
304# The length of the traffic checking period.
305
306max_days = 2
307
308# The number of unique IP addresses that must visit the channel during traffic checking
309
310unique_joins = 3
311
312# The total number of joins needed in traffick checking. This is a full sum.
313
314joins = 5
315
316# The number of supporters required to have at least 1 joincount during traffic checking.
317# This value is less or equal than required_supporters
318
319min_supporters = 3
320
321# The minimum joincount required for each supporter during traffic checking.
322# If any supporter has a lower joincount than this value, will result in a reject.
323
324min_supporters_joins = 1
325
326# Number of days for notification
327
328notify_days = 1
329
330# Number of days waiting for supporters confirmation
331
332support_days = 1
333
334# Reviewer's user_id
335
336reviewer_id = 1
337
338# Where to log application channel's stages, and other The Judge announces.
339# if set to 0 will log to debug channel, otherwise to admin channel
340
341log_to_admin_console = 1;
342
343# chanfix servername to send and receive Oplist/Score requests/answers
344chanfix_servername = gnuworld6.undernet.org