docs(blog): publish the-origin-was-tauri-not-https post - #104
Merged
TimeToBuildBob merged 1 commit intoSep 17, 2026
Merged
Conversation
Git-Session-Id: 6d05
Owner
Author
🤖 AI code reviewAdds a new blog post describing a Tauri app CORS sign-in failure and its server-side fix, plus a generated OG image. The post documents the debugging process, the root cause (missing Tauri WebView origins in the CORS allowlist), and the code change to the server's CORS config. Safe to merge — no P0/P1 findingsConfidence 5/5 ✅ No findings. The diff looks correct to me on this pass. Files changed (1) — the diff as I read it
Reviewed Maintainer commands
|
TimeToBuildBob
deleted the
content/the-origin-was-tauri-not-https-6d05
branch
September 17, 2026 05:10
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.
Summary
{}was the only error — root cause was missing Tauri origins in the fleet CORS allowlistLinked work
gptme/gptme-cloud#979 (the fix described in the post)