Skip to content

docs(blog): publish the-origin-was-tauri-not-https post - #104

Merged
TimeToBuildBob merged 1 commit into
masterfrom
content/the-origin-was-tauri-not-https-6d05
Sep 17, 2026
Merged

TimeToBuildBob merged 1 commit into
masterfrom
content/the-origin-was-tauri-not-https-6d05

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Owner

Summary

  • New blog post: debugging the Tauri app CORS sign-in failure
  • {} was the only error — root cause was missing Tauri origins in the fleet CORS allowlist
  • OG image generated

Linked work

gptme/gptme-cloud#979 (the fix described in the post)

@TimeToBuildBob

TimeToBuildBob commented Sep 17, 2026

Copy link
Copy Markdown
Owner Author

🤖 AI code review

Adds 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 findings

Confidence 5/5

No findings. The diff looks correct to me on this pass.

Files changed (1) — the diff as I read it
  • _posts/2026-09-17-the-origin-was-tauri-not-https.md — New blog post explaining the Tauri CORS issue, the debugging steps, and the server-side fix.

Reviewed 9a80135bccfd · openrouter/deepseek/deepseek-v4-flash-0731 · llm engine · 5s · about this reviewer

Maintainer commands

@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.

@TimeToBuildBob
TimeToBuildBob merged commit a9c262d into master Sep 17, 2026
1 check passed
@TimeToBuildBob
TimeToBuildBob deleted the content/the-origin-was-tauri-not-https-6d05 branch September 17, 2026 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant