Changelog
Keep yourself informed about the most recent additions and improvements
we’ve made to Sevalla.
Restart a database
You can now restart a database on demand from the dashboard. Open the database's Settings tab and click Restart database in the Danger zone.
The database is stopped and started again - existing connections are closed and any in-flight queries or uncommitted transactions are aborted. Stored data is preserved. The restart runs in the background and usually completes within a few minutes. The database is unavailable until it finishes.
Restart is available when the database is not suspended, is in a ready, error, passwordChangeFailed, or restoringFailed state, and its backup status is ready.
The same action is also available through the public API at POST /databases/{id}/restart-database and through the Sevalla CLI with sevalla databases restart {id}.
Header-based conditions in _redirects
Static site _redirects rules can now match on incoming request headers.
Add a Header:Name=value option at the end of a rule to apply it only when the request carries a matching header. For example, to serve a Markdown version of a page to clients that ask for it:
/quickstart/ /quickstart.md 301 Header:Accept=text/markdown
Header names are matched case-insensitively.
Restore a backup to a different database
You can now restore a database backup into a database other than the one it was taken from, making it easier to clone data between environments or recover into a fresh instance without overwriting the source.
When opening the Restore backup dialog, choose between:
- Restore to source - Replace the current data in the original database with the backup contents.
- Restore to different database - Pick any other compatible database in your company as the target.
Target databases must be the same type (for example, PostgreSQL), the same version, and in the same datacenter as the source. The source database is left untouched when restoring to a different target.
Delete non-empty object storage
You can now delete an object storage bucket even when it still contains objects. Any objects inside are removed automatically as part of the deletion.
Previously, you had to empty the bucket manually before it could be deleted.
Roll object storage secrets
You can now rotate the access and secret keys on an object storage bucket without taking your clients offline.
Open the bucket's Settings tab and click Roll secret in the Details section. Pick how long the previous keys should remain valid:
- Now - Invalidate the old keys immediately.
- Up to 168 hours - Keep the old keys working alongside the new ones during a grace period, then expire them automatically.
The new access and secret keys are shown right after rotation. Update your applications and tooling before the grace period ends so they switch over to the new credentials without disruption.
The same rotation is also available through the public API at POST /object-storage/{id}/rotate-credentials.