Files
galaxy/doc/source/admin/reports_options.rst
T
B0r1sD 0977c04216 Update citation to 2026 paper in `config_schema.yml`
Also:
- Apply config schema changes from
  https://github.com/galaxyproject/galaxy/pull/22910
- Update config and docs with `make config-rebuild` .
2026-07-03 12:30:14 +01:00

103 lines
2.0 KiB
ReStructuredText

~~~~~~~~~~~~~
``log_level``
~~~~~~~~~~~~~
:Description:
Verbosity of console log messages. Acceptable values can be found
here: https://docs.python.org/library/logging.html#logging-levels
:Default: ``DEBUG``
:Type: str
~~~~~~~~~~~~~~~~~~~~~~~
``database_connection``
~~~~~~~~~~~~~~~~~~~~~~~
:Description:
Database connection. Galaxy Reports are intended for production
Galaxy instances, so sqlite (and the default value below) is not
supported. An SQLAlchemy connection string should be used to
specify an external database.
:Default: ``sqlite:///./database/universe.sqlite?isolation_level=IMMEDIATE``
:Type: str
~~~~~~~~~~~~~
``file_path``
~~~~~~~~~~~~~
:Description:
Where dataset files are stored.
:Default: ``database/objects``
:Type: str
~~~~~~~~~~~~~~~~~
``new_file_path``
~~~~~~~~~~~~~~~~~
:Description:
Where temporary files are stored.
:Default: ``database/tmp``
:Type: str
~~~~~~~~~~~~~~~~~~~~~~~
``template_cache_path``
~~~~~~~~~~~~~~~~~~~~~~~
:Description:
Mako templates are compiled as needed and cached for reuse, this
directory is used for the cache
:Default: ``database/compiled_templates/reports``
:Type: str
~~~~~~~~~~~~~~~~~
``use_heartbeat``
~~~~~~~~~~~~~~~~~
:Description:
Write thread status periodically to 'heartbeat.log' (careful, uses
disk space rapidly!)
:Default: ``true``
:Type: bool
~~~~~~~~~~~~~~~
``smtp_server``
~~~~~~~~~~~~~~~
:Description:
Mail
:Default: ``yourserver@yourfacility.edu``
:Type: str
~~~~~~~~~~~~~~~~~~
``error_email_to``
~~~~~~~~~~~~~~~~~~
:Description:
Mail
:Default: ``your_bugs@bx.psu.edu``
:Type: str
~~~~~~~~~~~~~~~~~~~~
``enable_beta_gdpr``
~~~~~~~~~~~~~~~~~~~~
:Description:
Enables GDPR Compliance mode. This makes several changes to the
way Galaxy logs and exposes data externally such as removing
emails/usernames from logs and bug reports.
You are responsible for removing personal data from backups.
Please read the GDPR section under the special topics area of the
admin documentation.
:Default: ``false``
:Type: bool