fix some readme's

This commit is contained in:
Yannik Schmidt
2021-08-31 23:02:32 +02:00
parent b16d4c1e76
commit f0285baace

View File

@@ -2,9 +2,9 @@
server.py # the main flask server
app.py # the flask app wrapper that can be started via wsgi
scripts/ # user add/deletion scripts used for usermanagement
static/ # static files of the flask webserver (js/css etc.)
templates/ # jinja html templates used by the webserver (the actual webpages)
scripts/ # user add/deletion scripts used for user management
static/ # static files of the flask web-server (js/css etc.)
templates/ # jinja html templates used by the web-server (the actual web-pages)
setup.sh # remote setup script
aws/ # aws templates/files
@@ -14,10 +14,6 @@
- ssh
- rsync
## AWS
- awscli
# Remote Requirements
## Packages (APT)
@@ -50,6 +46,6 @@ The start script (*setup.sh*) performs the following task in this order:
The AWS-template setup uses git instead of rsync to pull the server files. The ssh-key fingerprint must be verified in advanced.
- create a keypair 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 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*)
- goto 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)
- 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)