From 6615b149c5e334302ee21b999183d86b55b4c0c3 Mon Sep 17 00:00:00 2001 From: Simon Vandevelde Date: Tue, 29 Dec 2020 20:04:48 +0100 Subject: [PATCH] Update README with wiki changes (#82) * Changed link to wiki * Removed unneeded links (as uWSGI won't be supported) * Added --host flag to uvicorn command, as the server is only accessible from the host machine otherwise (and not from another in the local network) --- README.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 1787a2f..c110672 100644 --- a/README.md +++ b/README.md @@ -62,18 +62,14 @@ Now you can initialise our django app. And you are done! You can now run the debug server just to see everything works as expected by running: ``` -uvicorn etebase_server.asgi:application --port 8000 +uvicorn etebase_server.asgi:application --host 0.0.0.0 --port 8000 ``` Using the debug server in production is not recommended, so please read the following section for a proper deployment. # Production deployment -There are more details about a proper production setup using Daphne and Nginx in the [wiki](https://github.com/etesync/server/wiki/Production-setup-using-Daphne-and-Nginx). - -Etebase is based on Django so you should refer to one of the following - * The instructions of the Django project [here](https://docs.djangoproject.com/en/2.2/howto/deployment/wsgi/). - * Instructions from uwsgi [here](http://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html). +There are more details about a proper production setup using uvicorn and Nginx in the [wiki](https://github.com/etesync/server/wiki/Production-setup-using-Nginx). The webserver should also be configured to serve Etebase using TLS. A guide for doing so can be found in the [wiki](https://github.com/etesync/server/wiki/Setup-HTTPS-for-Etebase) as well.