From 29c6c7de712d2d79a5e0edf75f9aa0c0389b196d Mon Sep 17 00:00:00 2001 From: Yannik Schmidt Date: Tue, 31 Aug 2021 23:08:45 +0200 Subject: [PATCH] add port/wsgi/service info to README --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 0b930b2..1babfaa 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ templates/ # jinja html templates used by the web-server (the actual web-pages) setup.sh # remote setup script aws/ # aws templates/files + flask-ftp.service # the systemd service used to start the webserver (change port and interface here) # Local Requirements ## setup.sh @@ -49,3 +50,7 @@ The AWS-template setup uses git instead of rsync to pull the server files. The s - create a key-pair called *"flask-ftp"* or change the value of *"KeyName"* in *aws/template.yml* to an existing key pair (see "AWS Network & Security -> Key Pairs" for details) - create a new stack (CloudFormation -> Stacks -> Create Stack) and upload the template (*aws/template.yml*) - go to Instances, select Security and click the security group, add inbound for the ports you want to use (e.g. FTP Ports, 80, 443 or 5000, allowing all for simplicity, is reasonably safe too in this case, since there's nothing running on the server except the public services) + +# Chaning port or interface + +The service is deployed via *"waitress"* and the startup command is defined in the *"ExecStart"*, including interface and port. You can swap out waitress for any other wsgi-server like *uwsgi* or *gunicorn*.