Release 0.2609.2
· One min read
This release expands database engine support and adds more control over database restarts and image versions.
Highlights:
- Added support for Valkey, ClickHouse, CouchDB, and MariaDB, with engine-specific configuration and connection details
- Added a database restart action with progress tracking and checks for conflicting operations
- Added an image-pinning action in database settings to retain the exact running image without restarting the database
- Improved database overview pages, connection information, and available-action feedback
Fixes:
- Prevented floating database image tags from silently selecting a different image during supported lifecycle operations
- Improved ClickHouse configuration for smaller CPU and memory allocations
- Improved database startup failure messages and version reporting
Notes:
- New database engines are enabled separately and appear in the creation form where available
- Image pinning preserves the current image; it does not upgrade the database
- ClickHouse exposes an HTTP client interface, CouchDB uses a single-node server, and MariaDB imports are not included