View of /trunk/cgi/defaultsettings.conf

### Do NOT edit this file directly, edit settings.conf instead or use the 
# change.py web interface.

### required variables
[required]

### nextevent - the time of the next event.
nextevent = Saturday

### location - location of the club, organization, or whatever
# i.e. where the event is held. If you have multiple possible locations, 
# seperate them each with a "," and it will be rendered as a ordered list. If
# the location otherwise contains commas, but you don't want them to be 
# rendered as seperate locations, surround the location with quotes
location = 123 ABC Street

### sitename - name of the site: i.e. the name of the club you are
# using a signup sheet for
sitename = Ultimate Frisbee

### createhtaccess - true or false value that determines if a .htaccess file
# should be created. if you are using Apache as your web server, PySignup can
# make a .htaccess file that will prevent web access of certain files, and
# make index.py the index file of PySignup's directory. The .htaccess file
# will only be created if it doesn't exist already. It is HIGHLY recommended
# to set this to true if using Apache, for security reasons!
createhtaccess = False

### datafields - fields that should be displayed to the viewer to fill in
# i.e. name and comment. This does not include password or CAPTCHA fields.
# This should be set as such: 
# "Name: pri, Comment: req, Phone: opt"
# seperate each field with a comma, and put either "pri", "opt" or "req" after
# the field name and a colon. "pri" means the field is the primary field, and
# will be required, "opt" will mean the field is not required, and
# "req" makes the field required (though not the primary field). The first 
# field should always be the primary field if using raw files for data storage,
# but can be any field when using a database (though the first is recommended)
# and there can only be one in either case. Also, do not change this after
# people have signed up without clearing the data first.
datafields = Name: pri, Comment: opt

### message - message to be displayed below location. useful for any comments
# you might wish to display to viewers
message =

### theme - name of the theme to be loaded by PySignup. Current theme names are
# black, grey, blue, and grass. Leave it blank for the default white theme, 
# with no extra CSS/JS loaded
theme = 

### userpass - one of three values: "optional", "required", or "none"
# optional will allow the viewer to enter a password if they like, but not
# require it, required will make the viewer enter a password, and none will
# not show the password box at all. 
# the password, if entered, will be required in order to later change that
# person's entry (i.e. remove them completely, or change their status)
userpass = optional

### storage - what storage method PySignup should use to store data. 
# currently, "sqlite" and "file" are the only available options.
# "sqlite" will use an SQLite database (requires PySQLite2)
# "file" will store all data directly in files (no requirements)
storage = file

### passhash - md5 hash of the system administrator's password. by default
# the password is "pysignup" - MAKE SURE TO CHANGE THIS! by clicking the 
# "change your password" link at the top of change.py, but do NOT edit this
# hash directly
passhash = A:CO09:d6f59f28d85173a32f5c3fa40bd70cba

### settings for the use of captchas, which help prevent spam
# currently recaptcha is the only available captcha to use
[captcha]

  # settings specifically for reCaptcha
  [[recaptcha]]

  ### userecaptcha - true or false value that determines if reCaptcha should
  # be used.
  userecaptcha = False
  
  ### publickey - the reCaptcha public key for your domain name. if you do 
  # not have one, get one here http://recaptcha.net/api/getkey
  publickey = 

  ### privatekey - the reCaptcha private key for your domain name. if you do
  # not have one, get one here http://recaptcha.net/api/getkey
  privatekey = 

  ### usecustom - whether or not a custom theme should be used with reCaptcha.
  # if false, you must specify one of the standard themes (red, white, clean,
  # or blackglass) in user.js
  usecustom = true

  ### reverseproxy - true or false value for if you are running PySignup
  # under a reverse proxy or not. if you don't know what this means, just
  # leave it as false. if true, a different method will be used to retrieve
  # the viewer's IP, since the normal method doesn't work properly with
  # reverse proxies.
  reverseproxy = False


### settings for the making a hyperlink that links to Google Maps
[googlemaps]

### usegooglemaps - either True or False variable that determines 
# whether the location should be a hyperlink to google maps
usegooglemaps = True

### full-location - full location of the next event, for example, including
# city, state, etc. optional value that is used for searching google maps,
# and if left blank, the value of location will be used instead. If you are 
# using multiple locations, seperate each full location by a "," If there are
# commas in the full location, and you don't want them rendered as seperate 
# locations, put each location in quotes.
full-location = 

### settings for optional mail sending
[mail]

### smtpserver - hostname of the server that PySignup should use to send mail
smtpserver = 

### mailuser - SMTP login name. this is only necessary if your smtpserver
# requires authentication
mailuser =

### mailpass - SMTP login password. this is only necessary if your smtpserver
# requires authentication
mailpass = 

# settings for sending alerts after certain events
[alerts]

### alerton - the minimum amount of people that must be signed up "in" for an
# alert (html or mail) to be sent
alerton = 8

### htmlalert - true or false value, if this is true, a message will appear
# when a certain number of people are "in" for the event
htmlalert = false

### htmltext - if htmlalert is true, this is the text that will be displayed
# when enough people have signed up
htmltext = Game On!

### mailalert - true or false value, if this is true, an email will be sent
# once a certain number of people are "in" for the event
mailalert = false

### toaddress - if mailalert is true, the address(es) that the email should be 
# sent too. seperate each email with a comma (,)
toaddress = mailing-list@example.com

### fromaddress - if mailalert is true, the address that should appear in the
# "from" header
fromaddress = example@example.com

### mailsubject - if mailalert is true, the subject of the email
mailsubject = Game On!

### mailbody - if mailalert is true, the body message of the email that will
# be sent
mailbody = Game is on!

# settings for using raw files to store data
[file]

### datafile - file name that signup data will stored in, this file should   
# probably be unaccessible from the web, either by being in a non-web
# directory, or by configuring your web server to deny access to it.
data-file = data.py
  
### sessionfile - file name that change.py sessions will be stored in, this
# file should be unaccessible from the web, as it contains hashes of admin
# session ids
session-file = sessions.py

# settings for using an SQLite database to store data
[sqlite]

# sqlitedb - file name of where the SQLite database should be stored. this
# should probably be unaccessible from the web.
sqlitedb = sqlitedb.py