[galaxy-commits] galaxy-dist commit 660a65d7c929: Add a few missing options to the sample config.
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Fri Jul 16 10:06:27 EDT 2010
# HG changeset patch -- Bitbucket.org
# Project galaxy-dist
# URL http://bitbucket.org/galaxy/galaxy-dist/overview
# User Nate Coraor <nate at bx.psu.edu>
# Date 1278099417 14400
# Node ID 660a65d7c9294284faaf6bc7b7c3a52d92d8c8d4
# Parent b841989e2662b204fcb4c73931ab3a2b08ef35a0
Add a few missing options to the sample config.
--- a/universe_wsgi.ini.sample
+++ b/universe_wsgi.ini.sample
@@ -75,6 +75,12 @@ paste.app_factory = galaxy.web.buildapp:
# [filter:proxy-prefix] section above.
#filter-with = proxy-prefix
+# If proxy-prefix is enabled and you're running more than one Galaxy instance
+# behind one hostname, you will want to set this to the same path as the prefix
+# in the filter above. This value becomes the "path" attribute set in the
+# cookie so the cookies from each instance will not clobber each other.
+#cookie_path = None
+
# -- Database
# By default, Galaxy uses a SQLite database at 'database/universe.sqlite'. You
@@ -93,6 +99,15 @@ paste.app_factory = galaxy.web.buildapp:
# you will want to set this to some positive value (7200 should work).
#database_engine_option_pool_recycle = -1
+# If large database query results are causing memory or response time issues in
+# the Galaxy process, leave the result on the server instead. This option is
+# only available for PostgreSQL and is highly recommended.
+#database_engine_option_server_side_cursors = False
+
+# Create only one connection to the database per thread, to reduce the
+# connection overhead. Recommended when not using SQLite:
+#database_engine_option_strategy = threadlocal
+
# -- Files and directories
# Dataset files are stored in this directory.
More information about the galaxy-commits
mailing list