From 2756f30eb4d984a6913a20fefb76729792abb40f Mon Sep 17 00:00:00 2001 From: Tom Hacohen Date: Thu, 28 Jun 2018 16:39:48 +0100 Subject: [PATCH] Revert "Mention setting up CORS in Readme" This is better solved by de4f49973f08027f0818c5780dd65517eb3c575e This reverts commit dfc7c8b1639710a6a03712c65c7ef14dd2a4237b. --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 8b0a26e..525d220 100644 --- a/README.md +++ b/README.md @@ -46,8 +46,6 @@ And you are done! You can now either run the debug server just to see everything Using the debug server in production is not recommended, so you should configure your webserver to serve etesync (with TLS). An example on how to do so with nginx can be found [here](http://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html). -If you plan to use the webclient, you also want to enable CORS in your nginx config. You can find a "wide -open CORS config" example [here](https://enable-cors.org/server_nginx.html) to be adjusted to your needs. # Usage