PapaTutuWawa/etesync-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

README: Added links pointing to specific wikipages

Browse Source 
* Added links pointing to the wiki.

I added a link for the deployment setup and one for the TLS setup.

Fixes #35
This commit is contained in:
Simon Vandevelde 2020-02-03 20:11:16 +01:00 committed by GitHub
parent 8c71bcddca
commit 1a04d8ec6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -75,9 +75,10 @@ EteSync is based on Django so you should refer to one of the following
* Instructions from uwsgi [here](http://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html). * Instructions from uwsgi [here](http://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html).
* The [example configurations](example-configs) in this repo. * The [example configurations](example-configs) in this repo.
The webserver should also be configured to serve EteSync using TLS. There are more details about a proper production setup using uWSGI and Nginx in the [wiki](https://github.com/etesync/server/wiki/Production-setup-using-uWSGI-and-Nginx).
There are more details about a proper production setup in the [wiki](https://github.com/etesync/server-skeleton/wiki). The webserver should also be configured to serve EteSync using TLS.
A guide for doing so can be found in the [wiki](https://github.com/etesync/server/wiki/Setup-HTTPS-for-EteSync) as well.
# Usage # Usage