Clarify tool source storage activation docs

This commit is contained in:
mvdbeek
2026-07-13 10:27:00 +02:00
parent 4151167386
commit 31ee132bfb
4 changed files with 17 additions and 17 deletions
+4 -4
View File
@@ -427,10 +427,10 @@
:Description:
SQLAlchemy connection string for storing pre-parsed tool sources.
The store is a rebuildable cache that lives outside Galaxy's
database. Defining this URI does not make Galaxy's eager toolbox
startup use the store; it is opened by code paths that explicitly
use tool source storage, such as the population script and lazy
toolbox consumers.
database. This URI is used by tool source storage code paths,
including the population script and lazy toolbox consumers.
Runtime use also requires a populated store and a toolbox consumer
configured to read from tool source storage.
By default, Galaxy uses a SQLite database at
``<data_dir>/tool_sources.sqlite``. Multi-host deployments should
point every process at the same SQLAlchemy URI, such as a SQLite
+5 -5
View File
@@ -38,11 +38,11 @@ Default Store
tool_source_database_connection: sqlite:////srv/galaxy/tool_sources.sqlite
The store lives in a standalone database - a SQLite file under
``<data_dir>/tool_sources.sqlite`` by default - never in Galaxy's own database. It is
a rebuildable cache: deleting it costs one populator run. Defining this URI
does not make Galaxy's eager toolbox startup use the store; it is opened by
code paths that explicitly use tool source storage, such as the population
script and lazy toolbox consumers.
``<data_dir>/tool_sources.sqlite`` by default - separate from Galaxy's main
database. It is a rebuildable cache: deleting it costs one populator run.
This URI is used by tool source storage code paths, including the population
script and lazy toolbox consumers. Runtime use also requires a populated store
and a toolbox consumer configured to read from tool source storage.
.. code-block:: yaml
+4 -4
View File
@@ -590,10 +590,10 @@ galaxy:
# SQLAlchemy connection string for storing pre-parsed tool sources.
# The store is a rebuildable cache that lives outside Galaxy's
# database. Defining this URI does not make Galaxy's eager toolbox
# startup use the store; it is opened by code paths that explicitly
# use tool source storage, such as the population script and lazy
# toolbox consumers.
# database. This URI is used by tool source storage code paths,
# including the population script and lazy toolbox consumers. Runtime
# use also requires a populated store and a toolbox consumer
# configured to read from tool source storage.
# By default, Galaxy uses a SQLite database at
# ``<data_dir>/tool_sources.sqlite``. Multi-host deployments should
# point every process at the same SQLAlchemy URI, such as a SQLite
+4 -4
View File
@@ -328,10 +328,10 @@ mapping:
desc: |
SQLAlchemy connection string for storing pre-parsed tool sources.
The store is a rebuildable cache that lives outside Galaxy's
database. Defining this URI does not make Galaxy's eager toolbox
startup use the store; it is opened by code paths that explicitly
use tool source storage, such as the population script and lazy
toolbox consumers.
database. This URI is used by tool source storage code paths,
including the population script and lazy toolbox consumers. Runtime
use also requires a populated store and a toolbox consumer configured
to read from tool source storage.
By default, Galaxy uses a SQLite database at
``<data_dir>/tool_sources.sqlite``. Multi-host deployments should point