Skip to content

Overview

Concepts and Principles

Development

Overview

IDEs

API Explorer

Releases

Release Notes

TORO Integrate

Coder Studio

Coder Cloud

Bug Reports

Search

Core Database Connections

Databases are mandatory in the implementation of some features of TORO Integrate. These required databases are what we call "core databases". By default, TORO Integrate creates these databases for you albeit in the form of embedded HSQL databases which, in most cases, is not ideal for production environments and warrants migration.

TORO Integrate's core databases are:

  • tracker

    The tracker database is used to store all Tracker-related data. It is also used when the Tracker Search Index needs to be rebuilt, in case the tracker index gets corrupted.

  • coder

    This database is mainly used for building reports.

  • flux

    Used for storing all Flux-related data.

  • config

    Used for storing created Integrate data such as Integrate Users (and the access tokens related to it), Integrate User Groups, and Monitor Rules.

Other pre-configured database connections

Any other database connection that is pre-configured but not a core database connection are most likely created and used by the examples package. It does not affect the functionality of TORO Integrate in any way and can be safely deleted if desired.

Like regular databases, TORO Integrate communicates with core databases via database connections. We call database connections of core databases, "core database connections". Core database connections are also pre-configured in TORO Integrate.

As Seen in the UI

In Coder, your instance's existing database connections can be shown by expanding the Databases sub-tree in the Coder Navigator view. In the Server Admin UI, they are listed in the Databases page.

Core database connections

Core database connections

Core database connections

Behaviors

Like any other database connection, the core database connections' statuses can be changed, however, keep in mind that there are a few key differences.

Although core database connections can be stopped so that they could be re-configured or migrated, deleting a core database connection would only reset its configuration to its default counterpart. Meanwhile, disabling core database connections is not possible because TORO Integrate requires these databases to run.

Error messages shown after an attempt to disable core database connections

In addition to this, any changes made to core database connections would require you to restart TORO Integrate.

Stop core database connections with caution

Stopping any of the core database connections would cause some functions to not work properly in TORO Integrate.