Configuration of dtable-server¶

This is a cheat sheet for the possible configuration options of dtable-server. It contains all possible settings that can be configured as well as their default values.

The default values provided here are best-effort (not built automatically). They will be used, if no value is defined at all. It is not necessary the value, that is written in the configuration file on first startup.

In the default values below, a value in the form $XYZ refers to an environment variable.

Environment Variables¶

This section lists the environment variables read by dtable-server.

Please note that these variables are not included in seatable-server.yml by default. We recommend that you do not modify the included *.yml files since any changes will be removed when upgrading SeaTable. Instead, add an additional custom-seatable-server.yml file that includes the additional environment variables:

services:
  seatable-server:
    environment:
      - AUTOMATION_RATE_LIMIT_PER_BASE_MINUTE=100

This file then needs to be added to the COMPOSE_FILE variable inside your .env file. This ensures that SeaTable upgrades stay seamless.

Automations¶

Configuration File¶

The following section describes the structure and possible configuration values of the configuration file dtable_server_config.json.

Example configuration

By default, dtable_server_config.json will be empty after the first startup of SeaTable:

{}

Redis¶

Persistence¶

dtable-server keeps bases in memory. After a certain time, the bases are persisted to storage (via dtable-storage-server).

Service URLs¶

Row Limits¶

Please note that increasing this value requires corresponding updates in dtable_web_settings.py, as detailed here.

Base Size Limit¶

Expert Configuration¶

It is not recommended to change these values

Cluster Setup¶

For more information on setting up a SeaTable cluster, which is typically suitable for systems supporting hundreds of users, please contact us.

Deprecated settings¶

Automation Limits¶

The setting per_minute_trigger_limit, which allowed limiting the number of automations that could be triggered per base per minute, has been removed in v6.1. You can use the environment variable AUTOMATION_RATE_LIMIT_PER_BASE_MINUTE instead if you want to modify the default setting.

MariaDB Database Connection¶

dtable-server used to read the database connection settings from dtable_server_config.json. Since version 5.3, dtable-server reads these settings from environment variables instead.

Redis Connection¶

dtable-server used to read the Redis connection settings from dtable_server_config.json. Since version 5.3, dtable-server reads these settings from environment variables instead.

Private Key¶

Starting with version 5.3, it is no longer required to provide private_key that is used to sign JWTs inside the configuration file. dtable-server reads this value from the JWT_PRIVATE_KEY environment variable instead.

API-Limits¶

The API limits mentioned are no longer applicable. Prior to SeaTable version 5.2, separate API limits existed for dtable-server and dtable-db. However, starting with version 5.2, API requests are now handled by the api-gateway, which enforces unified API limits across the platform.

Slave-Mode and Database-Split¶

These functions are deprecated and not maintained further.