Setting up Discourse CORS is not documented #1

Open
opened 2020-02-05 14:08:44 +01:00 by yala · 1 comment

This plugin assumes that a linked Discourse instance has CORS enabled for its domain, and eventually for localhost to ease development.

Steps needed to achieve this setting could be exemplified in the README, in so third parties can more easily reuse this code.

This plugin assumes that a linked Discourse instance has CORS enabled for its domain, and eventually for localhost to ease development. Steps needed to achieve this setting could be exemplified in the README, in so third parties can more easily reuse this code.
Owner

Yes good advice.
In discourse admin, under /admin/site_settings/category/security there is an option to enable CORS for all domains wanted.
I will update the readme...
Thx!

Yes good advice. In discourse admin, under `/admin/site_settings/category/security` there is an option to enable CORS for all domains wanted. I will update the readme... Thx!
This repo is archived. You cannot comment on issues.
No Label
No Milestone
No Assignees
2 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ManUtopiK/carteG1#1
No description provided.