From 2ba4dcaad55adc52a6d3859031de03a4b9689477 Mon Sep 17 00:00:00 2001 From: Pierre-Alain TORET Date: Mon, 11 May 2020 15:47:26 +0200 Subject: [PATCH] Fix links to next steps --- Production-setup-using-uWSGI-and-Nginx.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Production-setup-using-uWSGI-and-Nginx.md b/Production-setup-using-uWSGI-and-Nginx.md index a0883c3..8f2d507 100644 --- a/Production-setup-using-uWSGI-and-Nginx.md +++ b/Production-setup-using-uWSGI-and-Nginx.md @@ -150,7 +150,7 @@ uwsgi --ini uwsgi.ini You now have a working EteSync server over HTTP. Don't forget to change `allowed_hosts` to your domain name in `etesync-server.ini` and to set `server_name` to your domain name in `/etc/nginx-sites-available/etesync.conf`. -An optional next step is to have your uWSGI run automatically at boot. More explanation can be found here: [Run uWSGI at boot](../Run-uWSGI-at-boot) +An optional next step is to have your uWSGI run automatically at boot. More explanation can be found here: [Run uWSGI at boot](https://github.com/etesync/server/wiki/Run-uWSGI-at-boot) It is also *highly* recommended **to enable SSL for your EteSync server!** -A page detailing SSL setup can be found here: [Setup HTTPS for EteSync](../Setup-HTTPS-for-EteSync) \ No newline at end of file +A page detailing SSL setup can be found here: [Setup HTTPS for EteSync](https://github.com/etesync/server/wiki/Setup-HTTPS-for-EteSync) \ No newline at end of file