readme file updates
This commit is contained in:
@@ -1 +1 @@
|
|||||||
# TODO: ...
|
TODO: #14 Insert Authelia Readme
|
||||||
@@ -18,7 +18,7 @@ It's not secure to expose InfluxDB via the HTTP protocol. Follow these steps to
|
|||||||
|
|
||||||
### (Option 1): Upload custom certificates
|
### (Option 1): Upload custom certificates
|
||||||
|
|
||||||
TODO: Not tested in Docker-Compose...
|
TODO: #15 Test Docker-Compose for InfluxDB2
|
||||||
|
|
||||||
- [ ] Run the container with tls parameters
|
- [ ] Run the container with tls parameters
|
||||||
`influxd --tls-cert=/etc/ssl/cert.pem --tls-key=/etc/ssl/cert-key.pem`
|
`influxd --tls-cert=/etc/ssl/cert.pem --tls-key=/etc/ssl/cert-key.pem`
|
||||||
|
|||||||
27
docker-compose/nginxproxymanager/README.md
Normal file
27
docker-compose/nginxproxymanager/README.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
# Installation
|
||||||
|
|
||||||
|
## Deployment
|
||||||
|
|
||||||
|
Copy the `docker-compose.yml` template into your project folder and start the container.
|
||||||
|
|
||||||
|
## Configuration
|
||||||
|
|
||||||
|
Visit the Nginxproxymanager Web Interface `http://localhost:81`, and login with Nginxproxymanager's default username `admin@example.com` and password: `changeme`.
|
||||||
|
|
||||||
|
*For more info visit:* [Official Nginxproxymanager Installation Documentation](https://nginxproxymanager.com/guide/)
|
||||||
|
|
||||||
|
# Best-Practices & Post-Installation
|
||||||
|
|
||||||
|
## Disable HTTP
|
||||||
|
|
||||||
|
It's not secure to expose Nginxproxymanager via the HTTP protocol. Follow these steps to enable HTTPS only.
|
||||||
|
|
||||||
|
### Don't expose Nginxproxymanager's UI on port 81
|
||||||
|
|
||||||
|
- [ ] Add a Proxy Host for Nginxproxymanager's WebUI to target `127.0.0.1:81`
|
||||||
|
- [ ] Remove port `:81` from the `docker-compose` file
|
||||||
|
|
||||||
|
|
||||||
|
# Additional Referfences
|
||||||
|
|
||||||
|
[Official Nginxproxymanager Installation Documentation](https://nginxproxymanager.com/guide/)
|
||||||
Reference in New Issue
Block a user