ComputerSurge/shields
3
0
Fork 0
Code Pull Requests 1 Activity

Allow configuring allowed CORS origins for suggest (#1282)

Browse Source 
- Support single-server testing and a local dev server (like Next) that is on a different port from the shields server
- Refactor config schema

With this change, the suggestions work locally in #1273.
This commit is contained in:
Paul Melnikow
2017-11-25 18:27:02 -05:00
committed by GitHub
parent a4bce73da6
commit 1af1f497bb
4 changed files with 80 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/self-hosting.md
View File

@@ -139,8 +139,17 @@ If you want to host the frontend on a separate server, such as cloud storage
or a CDN, you can do that. Just copy the built `index.html` there.
To help out users, you can make the Shields server redirect the server root.
Set the `FRONTEND_REDIRECT_URL` environment variable:
Set the `REDIRECT_URI` environment variable:
```sh
FRONTEND_REDIRECT_URL=http://my-custom-shields.s3.amazonaws.com/
REDIRECT_URI=http://my-custom-shields.s3.amazonaws.com/
```
If you want to use server suggestions, you should also set `ALLOWED_ORIGIN`:
```sh
ALLOWED_ORIGIN=http://my-custom-shields.s3.amazonaws.com,https://my-custom-shields.s3.amazonaws.com
```
This should be a comma-separated list of allowed origin headers. They should
not have paths or trailing slashes.