# AN IMPORTANT NOTE ABOUT YAML CONFIGURATION FILES:
# !!! Be sure to use spaces instead of tabs for indentation, as YAML is very
# !!! sensitive to white-space inconsistencies!

##### HTTP SERVER #####################################################################

# Under what HTTP environment are you running the Cloudmasterd server? The following methods
# are currently supported:
#
# webrick -- simple stand-alone HTTP server; this is the default method
# mongrel -- fast stand-alone HTTP server; much faster than webrick, but 
#            you'll have to first install the mongrel gem
# 

### webrick example

server: webrick
port: 8106

### webrick SSL example

#server: webrick
#port: 443
#ssl_cert: /path/to/your/ssl.pem

# if the private key is separate from cert:
#ssl_key: /path/to/your/private_key.pem


### mongrel example

#server: mongrel
#port: 8106

# It is possible to run mongrel over SSL, but you will need to use a reverse proxy
# (try Pound or Apache).


##### DATABASE ########################################################################

# The Blog needs a database to store its records.
# 
# By default, we use MySQL, since it is widely used and does not require any additional
# ruby libraries besides ActiveRecord.
#
# With MySQL, your config would be something like the following:
# (be sure to create the blog database in MySQL beforehand,
#   i.e. `mysqladmin -u root create blog`)

#database:
#  adapter: mysql
#  database: blog
#  username: root
#  password: 
#  host: localhost


# Instead of MySQL you can use SQLite3, PostgreSQL, MSSQL, or anything else supported 
# by ActiveRecord.
#
# If you do not have a database server available, you can try using the SQLite3
# back-end. SQLite3 does not require it's own server. Instead all data is stored
# in local files. For SQLite3, your configuration would look something like the
# following (don't forget to install the 'sqlite3-ruby' gem first!):
#
#database:
#  adapter: sqlite3
#  dbfile: /var/lib/blog.db

##### GENOMED ########################################################################


##### LOGGING #########################################################################

# This log is where you'll want to look in case of problems. 
# 
# By default, we will try to create a log file named 'blog.log' in the current 
# directory (the directory where you're running the blog from). A better place to put 
# the log is in /var/log, but you will have to run blog as root or otherwise give 
# it permissions.
# 
# Set the level to DEBUG if you want more detailed logging. Other options are
# INFO, WARN, and ERROR (DEBUG is most verbose, ERROR is least).

log:
  level: DEBUG
  file: /var/log/genomed.log
#  level: INFO