Upgrade GoToSocial configuration to 0.20.2 #206

Merged

skobkin merged 1 commit from gotosocial_upgrade_0.20.2 into master

2026-01-12 21:00:16 +03:00

skobkin commented

2026-01-12 20:57:15 +03:00

Owner

Description

This PR updates the distributed environment configuration template to align with GoToSocial ≥ 0.20.x and fixes several deprecated or incorrect variables introduced in earlier versions.

Summary of changes

Database configuration

Fix invalid Postgres variable name
- Renamed GTS_DB_NAME → GTS_DB_DATABASE
- This variable is required in 0.20.x and the old name is no longer recognized.

Logging

Explicitly set log output format
- Added GTS_LOG_FORMAT=json to avoid relying on implicit defaults and to improve log ingestion compatibility with structured logging systems.

Instance exposure settings (breaking changes in 0.20.x)

Renamed deprecated “suspended” exposure variables
- GTS_INSTANCE_EXPOSE_SUSPENDED → GTS_INSTANCE_EXPOSE_BLOCKLIST
- GTS_INSTANCE_EXPOSE_SUSPENDED_WEB → GTS_INSTANCE_EXPOSE_BLOCKLIST_WEB
Added new optional exposure flags introduced in 0.20.x
- GTS_INSTANCE_EXPOSE_ALLOWLIST
- GTS_INSTANCE_EXPOSE_ALLOWLIST_WEB
- GTS_INSTANCE_EXPOSE_CUSTOM_EMOJIS

Statuses & media

Documented (commented) new configuration options:
- GTS_MEDIA_THUMB_MAX_PIXELS
- Scheduled status limits:
  - GTS_SCHEDULED_STATUSES_MAX_TOTAL
  - GTS_SCHEDULED_STATUSES_MAX_DAILY

Storage / cache

Documented (commented) new S3 optimization option:
- GTS_CACHE_S3_OBJECT_INFO

Rationale

These changes ensure:

Compatibility with GoToSocial 0.20.x breaking configuration changes
Correct Postgres configuration when using environment variables
Explicit, predictable defaults for logging and instance exposure
Visibility of new optional settings without changing runtime behavior

No functional behavior is changed unless the newly added (commented) variables are explicitly enabled.

## Description This PR updates the distributed environment configuration template to align with **GoToSocial ≥ 0.20.x** and fixes several deprecated or incorrect variables introduced in earlier versions. ### Summary of changes #### Database configuration - **Fix invalid Postgres variable name** - Renamed `GTS_DB_NAME` → `GTS_DB_DATABASE` - This variable is required in 0.20.x and the old name is no longer recognized. #### Logging - **Explicitly set log output format** - Added `GTS_LOG_FORMAT=json` to avoid relying on implicit defaults and to improve log ingestion compatibility with structured logging systems. #### Instance exposure settings (breaking changes in 0.20.x) - **Renamed deprecated “suspended” exposure variables** - `GTS_INSTANCE_EXPOSE_SUSPENDED` → `GTS_INSTANCE_EXPOSE_BLOCKLIST` - `GTS_INSTANCE_EXPOSE_SUSPENDED_WEB` → `GTS_INSTANCE_EXPOSE_BLOCKLIST_WEB` - **Added new optional exposure flags introduced in 0.20.x** - `GTS_INSTANCE_EXPOSE_ALLOWLIST` - `GTS_INSTANCE_EXPOSE_ALLOWLIST_WEB` - `GTS_INSTANCE_EXPOSE_CUSTOM_EMOJIS` #### Statuses & media - Documented (commented) new configuration options: - `GTS_MEDIA_THUMB_MAX_PIXELS` - Scheduled status limits: - `GTS_SCHEDULED_STATUSES_MAX_TOTAL` - `GTS_SCHEDULED_STATUSES_MAX_DAILY` #### Storage / cache - Documented (commented) new S3 optimization option: - `GTS_CACHE_S3_OBJECT_INFO` ### Rationale These changes ensure: - Compatibility with GoToSocial 0.20.x breaking configuration changes - Correct Postgres configuration when using environment variables - Explicit, predictable defaults for logging and instance exposure - Visibility of new optional settings without changing runtime behavior No functional behavior is changed unless the newly added (commented) variables are explicitly enabled.

skobkin added the

bug

enhancement

labels

2026-01-12 20:57:15 +03:00

skobkin self-assigned this

2026-01-12 20:57:15 +03:00

skobkin added 1 commit

2026-01-12 20:57:15 +03:00

Upgrade GoToSocial configuration to 0.20.2

ci/woodpecker/pr/validate Pipeline was successful

Details