Remove command generate-tls-cert

docs/Commands.md

@@ -25,11 +25,6 @@ This sets up some database tables, views, and more, generates a secret key for t
 
 ---
 
-`generate-tls-cert` - generate a new self-signed tls certificate for https  
-This overwrites the original files, if present (see [Setup](Setup.md)).
-
----
-
 `generate-secret-key` - generate a new random secret key for django  
 This will overwrite the old one.  
 Warning: After running this, current sessions will be invalid, and the users have to relogin. Don't run this command while the server is running.

docs/Configuration.md

@@ -7,15 +7,6 @@
 There is no default configuration available, only a sample configuration with explanations.
 
 
-## Configuration files for tls certificates
-
-This is the configuration for self-signed local TLS certificate generation.  
-
-`./config/tls/cert-config.sh`
-
-This is already configured, but you can modify this for your needs.
-
-
 ## Caddy Server Configuration  
 
 `./config/Caddyfile`  

docs/Setup.md

@@ -81,16 +81,8 @@ You can configure your database connection in `config/config.sh`.
 
 ## IV. HTTPS & TLS Certificates
 
-TLS/SSL certificates are required.
-If you don't have a TLS/SSL certificate already, you can generate one
-with the command `./run.sh generate-tls-cert`. This will generate a 
-new TLS certificate and key file at `config/tls/server.pem` (certificate)
-and `config/tls/server-key.pem` (key).  
-WARNING: This will overwrite an existing certificate/key with the same filepath.
-By default those generated certificates are valid for one year. After that year,
-they have to be regenerated with the same command.  
-
-If you have a certificate and key file already, you can put them in the following places:
+A TLS/SSL certificate and key is required.
+Filepaths:
 
 - `config/tls/server.pem` for the certificate 
 - `config/tls/server-key.pem` for the key