# sample /etc/jenovarc

# required: info about the mysql database that holds the user records
# any of these can be passed on the command-line, too.
#db-host: localhost
#db-user: say2
#db-pass: password
#db-name: say2

# or, you may choose the simpler route and store things in gdbm files
# (don't put a filename extension here; most dbm packages add their own,
# and we'll be using this filename root to create 2 to 4 files.)
gdbm-file: /etc/jenovadb

# specify the authoritative name for this host.  if omitted, jenova will try
# to figure it out.
#hostname: kitten.lag.net

# use 'alias' lines to add additional names (these will be listed as aliases
# for the server cert).
alias: say2.lag.net

# MOTD file (if any) to show to users when they login
motd: /etc/jenova.motd

# if you want logging, set this
#logfile: /var/log/jenova

# if run as root, jenova will immediately drop its root privs after reading
# the cert files and opening the listening port.  normally it will run as
# user "nobody", but you can set an alternate user here if you wish.
#run-as-user: nobody

# the following two lines are OPTIONAL.
# comment them out to turn off SSL support.
# here's a good way to make a new cert:
#     openssl req -newkey rsa:1024 -out say2-cert.der -outform der -keyout say2-key.pem -x509 -days 365 -nodes

# where's our public cert?
# (it should be in DER format)
certfile: /etc/say2-cert.der

# where's our private key?
# (it should be in normal PEM format)
keyfile: /etc/say2-key.pem

# if you want to include the system config (and have it possibly
# overwrite some of your config settings) put it here:
# $include /etc/jenovarc.local
