some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for 'database.example.com', # Set to empty string for default 'PORT': '', } } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

choices see SSL Mode De- scriptions POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. 2.1. Configuration instructions 139 The Weblate Manual some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings localhost "HOST": "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

that case you will have to perform some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: Configuring Weblate to use PostgreSQL The settings.py snippet for PostgreSQL: UTF8 -O weblate weblate CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; CREATE EXTENSION IF NOT EXISTS btree_gin WITH SCHEMA weblate; DATABASES = { "default": { # Database engine html#LIBPQ- SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. POSTGRES_CONN_MAX_AGE New in version 4.8.1. The

choices see SSL Mode De- scriptions POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. POSTGRES_CONN_MAX_AGE New in version 4.8.1. The only one instance should be running. This container is also responsible for the database structure migrations and it should be started prior others. celery-backup Celery worker for backups, only one instance manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; CREATE EXTENSION IF NOT EXISTS btree_gin WITH SCHEMA weblate; Configuring Weblate to

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for 'database.example.com', # Set to empty string for default 'PORT': '', } } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush

some of the migration steps manually as a PostgreSQL superuser in schema Weblate will use: CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA weblate; Configuring Weblate to use PostgreSQL The settings html#LIBPQ-SSL-SSLMODE-STATEMENTS] POSTGRES_ALTER_ROLE Configures name of role to alter during migrations, see Configuring Weblate to use PostgreSQL. Database backup settings See also Dumped data for "database.example.com", # Set to empty string for default "PORT": "", }, } 2. Run migrations and drop any data inserted into the tables: weblate migrate --database=postgresql weblate sqlflush