fix(plane): add http scheme to WEB_URL

[adryserage]

Summary

• Add \http://\ scheme to \WEB_URL\ so Plane can generate valid links (emails, redirects, etc.)
• Uses \http://\ instead of \https://\ since Traefik handles SSL termination

Changes

• \�lueprints/plane/template.toml: \WEB_URL=\ → \WEB_URL=http://\

Context

Follows up on #582 (closed for inactivity). Addresses review feedback from @Siumauricio — removed \https://\ and kept \API_BASE_URL\ as internal \http://api:8000\.

Testing

Verified template.toml syntax is valid.

Greptile Summary

Added http:// scheme to WEB_URL environment variable so Plane can generate valid absolute URLs for emails, redirects, and other features. The change correctly uses http:// instead of https:// since Traefik handles SSL termination at the proxy level.

• Fixed WEB_URL to include http:// scheme prefix (was missing protocol entirely)
• Change follows repository conventions - many templates use http://${domain} pattern for internal URLs
• One potential issue: CORS_ALLOWED_ORIGINS still uses https:// which may cause CORS errors

Confidence Score: 4/5

• Safe to merge with one CORS configuration issue to verify
• The change is minimal, well-justified, and follows repository conventions for handling SSL termination. Score is 4 instead of 5 due to potential CORS mismatch between WEB_URL (http) and CORS_ALLOWED_ORIGINS (https) that should be verified in testing
• Verify CORS_ALLOWED_ORIGINS configuration in production to ensure no CORS errors occur

_{Last reviewed commit: 36194c6}

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	658853e

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

blueprints/plane/template.toml
CORS_ALLOWED_ORIGINS uses https:// but WEB_URL on line 12 uses http://. If Traefik handles SSL termination, CORS might block requests since the browser sees https but backend expects http origins.

"CORS_ALLOWED_ORIGINS=http://${Domain}",

[Copilot]

Pull request overview

Updates the Plane blueprint’s environment configuration to ensure WEB_URL includes an explicit http:// scheme, so Plane can generate valid absolute links when deployed behind Dokploy/Traefik.

Changes:

• Set WEB_URL to http://… instead of a schemeless value in Plane’s template.toml.

[Copilot]

WEB_URL is being built with ${Domain}, but Domain is only an env var entry ("Domain=...") and is not defined under [variables]. As a result, Dokploy interpolation likely won’t replace ${Domain}, leaving the literal string http://${Domain} and breaking Plane’s generated links. Use ${main_domain} (or ${domain}) directly in WEB_URL (and avoid referencing other env vars inside ${...}).

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.