Skip to content

Scheduled backups to Stroke Cloud or your own S3 - #290

Merged
broisnees merged 2 commits into
nightlyfrom
scheduled-backups
Nov 18, 2026
Merged

broisnees merged 2 commits into
nightlyfrom
scheduled-backups

Conversation

@broisnees

Copy link
Copy Markdown
Collaborator
  • Scheduled tab in Backup: up to 10 schedules per Pro account (hourly, every 6 hours, daily, weekly or a cron), saved to Stroke Cloud (R2, 5 GB, keeps the last N) or any S3-compatible bucket. S3 keys stay in the keychain vault.
  • Runs in the app on the computer that has the saved connection: a standalone connection, a gzip of the backup engine's dump, then a chunked upload to stroke.click or one signed PUT to S3. The server claims each tick, so two computers never run the same one. Missed ticks run once when the app opens, and "Run now" from the website is picked up within two minutes.
  • Supports PostgreSQL, MySQL, SQLite, D1, Turso/libSQL, DuckDB and SQL Server.
  • The app now sends its version with account checks, so the device list on the website shows what each computer runs.
  • Lockfile: restored the cc entry for libduckdb-sys.

Server side is live (stroke-web #65). Tests: vitest 1805 passed (incl. dueSlot and describeCron), cloud_backup and dynamodb Rust tests pass, svelte-check 0 errors, design lint clean.

@broisnees
broisnees merged commit 8406f11 into nightly Nov 18, 2026
1 check passed
@broisnees
broisnees deleted the scheduled-backups branch November 18, 2026 06:15
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant