# =======================================================
# Properties file for the Mindquarry Collaboration Server
# =======================================================

# Displayed on login page and in the title of each webpage
mindquarry.title=Mindquarry Example

# Must be the one and only domain name or ip (plus port, if not 80) under
# which the server is available to browsers and other clients. Will be used
# for absolute URLs in the web content, so make sure it is correct!
mindquarry.server.url=http://your.mindquarry.server

# JCR (main DB for users/teams/wiki/tasks/talk)
# =============================================
# windows example: file:/C:/Dokumente und Einstellungen/alexs/mindquarry/repo
mindquarry.jcr.path=file:/var/mindquarry/repo
mindquarry.jcr.login=admin
mindquarry.jcr.pwd=hierkommtkeinerdrauf

# Solr (full text index)
# ======================
# windows example: C:\\Dokumente und Einstellungen\\alexs\\mindquarry\\index
mindquarry.solr.path=/var/mindquarry/index
mindquarry.solr.login=solr
mindquarry.solr.pwd=solr
mindquarry.solr.endpoint=http://your.mindquarry.server/solr/update

# Files (versioning, svn)
# =======================
# windows example: C:\\Dokumente und Einstellungen\\alexs\\mindquarry\\docs
mindquarry.repos.path=/var/mindquarry/docs
mindquarry.repos.uri=http://your.mindquarry.server/repos

# Team / User
# ===========
# enables (true) / disables (false) the login as anonymous
mindquarry.teams.enableAnonymousUser=false
# should be set to false for demo server
mindquarry.teams.enablePasswordChange=true 

# Conversations
# =============
mindquarry.mail.server=localhost

# Cocoon settings
# ===============

# General mode: dev (= development) or prod (= production)
# in dev mode sitemap reloading is on and loglevel is set to debug
# in prod mode both are turned off for better performance
org.apache.cocoon.mode=prod

# Profiling (only for testing, never for production!)
# NOTE: this property is CURRENTLY DISABLED (see spring bean config files
#       mindquarry-webapp-resources/META-INF/cocoon/spring/(dev|prod)/pipes.xml
#       to manually enable profiling and RunningModeDependentPipeline which
#       would read this property but is not configured)
#mindquarry.cocoon.profile=false

# Logging (log4j)
# ===============

# Everything from Cocoon and all Mindquarry components inside Cocoon will use
# log4j (typically via commons-logging). Only some early-running servlet
# listeners or filters use the standard servlet logging because the following
# log4j setup will be read by the servlet listener
# com.mindquarry.webapp.servlet.ConfigLoaderListener - before he is run,
# log4j is unconfigured and won't print anything.

# Documentation for log4j: http://logging.apache.org/log4j/docs/manual.html

# Note: Cocoon request processing exceptions are always logged onto the console.
# Note: Standard Cocoon sitemap components use "cocoon" as logger name
#       (ie. not the class name) - see below
# Note: Code that uses java.util.logging will be redirected to log4j (thanks
#       to com.mindquarry.webapp.Log4jHandler, created by ConfigLoaderListener);
#       logger names are the same as used in jdk logging, thus using
#       log4j.logger.<logger-name>=DEBUG works

# Tip: If you change the global log level, you end up with lots of messages by
#      all the cocoon components. For debugging certain things it is best to
#      specifically use a higher log level for that component (see below)
# Tip: If you want to debug log4j, set -Dlog4j.debug on the command line

# Global log level:
# If you only want to change the global log level, make sure your keep it in
# the format "log4j.rootLogger=<level>, mindquarry".
# Available levels from quiet to fully verbose:
# OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL
log4j.rootLogger=ERROR, mindquarry

# The file where all the log4j output goes to (on Mac use Konsole application
# to view log files in /var/log)
log4j.appender.mindquarry.File=/var/log/mindquarry.log

# Formatting the output in the standard log file
log4j.appender.mindquarry=org.apache.log4j.FileAppender
log4j.appender.mindquarry.layout=org.apache.log4j.PatternLayout
log4j.appender.mindquarry.layout.ConversionPattern=%d{ISO8601} %t %-5p %c - %m%n

# Custom component logging:
# To set the log level for a certain component to a separate value, use the
# pattern "log4j.logger.<logger-name>=DEBUG". Typically the <logger-name> is
# the class name of the class that logs.
#log4j.logger.com.mindquarry.user.manager.UserEntity=DEBUG
#log4j.logger.com.mindquarry.jcr.jackrabbit.setup.JackrabbitInitializer=DEBUG
#log4j.logger.org.apache.solr=DEBUG

# Cocoon components logging:
# All cocoon components share the same logger name "cocoon" (ie. those that
# use AbstractLogEnabled) - these are very many components
#log4j.logger.cocoon=DEBUG

# Management properties
# =====================
# these properties only apply when the non-open-source Mindquarry
# server management extension is available
mindquarry.management.server=platformServer
#mindquarry.management.server=standaloneServer
mindquarry.management.adaptor.html=true
mindquarry.management.adaptor.html.port=4444