FrameOS Cloud 3/4: scene and frame config backups#265
Open
mariusandra wants to merge 2 commits into
Open
Conversation
Phase 3 of CLOUD-TODO.md, on top of the link and cloud login: - Push scenes (as the template interchange zip) and sanitized frame configs to the linked provider; restore either from the settings page. Local machine credentials (SSH, TLS, admin auth, wifi/agent secrets) are stripped; app API keys are intentionally retained so restored scenes keep working - The backup scopes come with every cloud account, but nothing is uploaded until the matching local switch is turned on (backup_scenes_enabled / backup_frames_enabled + migration) - Automatic frame backup after every successful deploy, driven by the update_frame broadcast in the cloud sync worker; durable last_cloud_backup_deploy_at tracking (+ migration) so a worker restart neither re-uploads everything nor loses failed uploads - Local tarball export of all templates stays available without a link - templates.py: template zip build/parse refactor shared with the backup payloads, and exports now record the FrameOS version they were made with Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part 3 of the FrameOS Cloud stack (on top of the linking and login PRs; #257 with the store + cloud drive sits on top of this).
backup_scenes_enabled/backup_frames_enabled, + migration)update_framebroadcast in the cloud sync worker; durablelast_cloud_backup_deploy_attracking (+ migration) so a worker restart neither re-uploads every frame nor loses a failed uploadtemplates.py: the template zip build/parse refactor shared with the backup payloads; exports now record the FrameOS version they were made withTest plan
pytest test_cloud_backups.py app/cloud/tests/test_sync.py test_templates.py+ the earlier cloud suites — 60 passed (full backend suite: 780 passed)🤖 Generated with Claude Code