Changelog
Keep yourself informed about the most recent additions and improvements
we’ve made to Sevalla.
Bandwidth chart in analytics
Application and static site Analytics tabs now include a Bandwidth chart alongside the existing request rate, response time, and status code charts. Use it to see how much traffic your service is serving over time and to spot bandwidth spikes.
The same timeframe and filter controls that apply to the other charts apply to bandwidth as well.
Git LFS support
Applications and static sites can now pull LFS-tracked files when deploying from repositories that use Git Large File Storage (LFS). Large assets tracked by LFS - such as images, videos, datasets, or model files - are fetched during the build. Previously, deploys from LFS repositories succeeded but only the LFS pointer files were checked out, not the actual file contents.
Git LFS is enabled by default. You can disable or re-enable it from the application or static site Settings tab. The same flag is available through the public API as git_lfs_enabled on update application and update static site.
You can also toggle the flag with Sevalla CLI v1.10.0:
sevalla apps update {id} --git-lfs-enabled true
sevalla static-sites update {id} --git-lfs-enabled true
And in the Terraform provider v1.1.0.
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.