From 75c3462eae9cf2ac256a9d4276f37e24b83701e2 Mon Sep 17 00:00:00 2001 From: Linus Groh Date: Fri, 27 Sep 2019 19:19:38 +0100 Subject: [PATCH] Clarify cors-proxy usage --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 519bc63..48114be 100644 --- a/README.md +++ b/README.md @@ -25,9 +25,12 @@ pages, this is a more advanced interface with more functionality, all in one pla - Run `yarn lint` to lint and fix files You can use the [`corsProxy.js`](scripts/corsProxy.js) script to use your production -instance of OwnTracks for development without making changes to its CORS-Headers. +instance of OwnTracks for development without making changes to its CORS-Headers: -Run like this: +```console +$ yarn cors-proxy +``` +If you have [basic authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#Basic_authentication_scheme) enabled: ```console $ env OT_BASIC_AUTH_USERNAME=username OT_BASIC_AUTH_PASSWORD='P@$$w0rd' yarn cors-proxy