Repository navigation
Complete Flutter account sync, recovery and production deployment tooling - #1
Open
alikhansabargazy wants to merge 8 commits into
Open
alikhansabargazy wants to merge 8 commits into
alikhansabargazy wants to merge 8 commits into
Conversation
alikhansabargazy
changed the title
alikhansabargazy
changed the title
alikhansabargazy
changed the title
alikhansabargazy
marked this pull request as ready for review
October 29, 2026 05:51
This branch has not been deployed
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
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.
Personal Flutter planners now use the shared authenticated API with account-scoped cached data, persistent pending writes, retry and explicit conflict resolution. Guest import is explicit. Sessions use secure storage; mobile release clients require HTTPS. Random web-safe account IDs avoid reuse after deletion.
Add password change, password-confirmed deletion and single-use recovery codes with session revocation. Harden API validation, transaction acknowledgements, authorization transactions, worker limits and persistent auth limits. Add schema versioning, consistent SQLite backups with retention, a daily backup container, HTTPS Caddy deployment, monitoring script, release signing configuration and deployment/restore runbooks.
Validation: 13 API/operations tests and 5 Flutter tests pass locally. Flutter analyze reports no issues; release web build succeeds. GitHub checks built Android debug APK and release web, built the Docker image, validated Compose/Caddy and successfully started healthy API and backup containers. Latest backend-only ID fix is locally tested; its new CI run may still be pending. A 100-request health smoke test with 8 clients returned all 200s.
Deployment still requires actual domain/server configuration, off-host backup destination and alert webhook. Android distribution requires the owner's signing key; debug-key fallback was removed. Recovery is via a code saved beforehand, not email; email identifiers are unverified. No live deployment is claimed. See deploy/RELEASE_CHECKLIST.md.