Skip to content

docs(news): turnkey Waline deploy guide + SECURE_DOMAINS - #645

Open
romeo111 wants to merge 1 commit into
masterfrom
claude/news-comments-deploy-guide
Open

docs(news): turnkey Waline deploy guide + SECURE_DOMAINS#645
romeo111 wants to merge 1 commit into
masterfrom
claude/news-comments-deploy-guide

Conversation

@romeo111

Copy link
Copy Markdown
Owner

Follow-up to #643. Two improvements to the now-live comment setup guide:

  • Adds SECURE_DOMAINS=openonco.info to the required env vars. Without it, a Waline instance accepts posts from any origin — any site can point its comment box at the server and use it as a spam relay. This was missing from the original guide and is a real hardening gap, not a nicety.
  • Turns the deploy section into a copy-paste env-var block, with the two privacy choices pre-decided and explained: AKISMET_KEY=false (the default is a shared hardcoded key that ships every comment's text to a third party) and Neon in an EU region rather than China-hosted LeanCloud.

Verified against Waline's current Vercel deploy flow on 2026-07-20. Docs-only; no code or build change.

🤖 Generated with Claude Code

The live setup guide omitted SECURE_DOMAINS, which restricts posting to your own site — without it, any website can point its comment box at the server and use it as a spam relay. That is a real gap, not a nicety.

Also turns the deploy section into a copy-paste env-var block with the two privacy choices pre-decided (AKISMET_KEY=false so comment text is not sent to a shared third-party key; Neon in an EU region, not China-hosted LeanCloud), verified against Waline's current Vercel deploy flow on 2026-07-20.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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