docs: added configuration section which lists all environment variables that are available

Author: Bram Ceulemans

README.md

@@ -15,7 +15,7 @@ services:
     image: jwilder/whoami
     ports:
       - 8080:8000
-  
+
   disrupt:
     image: blamebutton/disrupt
     volumes:
@@ -32,9 +32,21 @@ For more examples, check out the [examples folder](/.examples)
 
 **Note**: Docker Swarm does not support running locally built images, so neither does Disrupt.
 
+## Configuration
+
+Configuration of Disrupt is done through environment variables. This is done to make the deployment of Disrupt
+environment-agnostic.
+
+Below is a list of environment variables available to be configured.
+
+| Name | Type | Options |
+| - | - | - |
+| UPDATE_DELAY | Integer | default = 300 |
+| NOTIFICATION_URL | String | Any [Apprise](https://github.com/caronc/apprise#popular-notification-services) compatible URL |
+
 ## Notifications
 
-Disrupt uses the [Apprise](https://github.com/caronc/apprise) notification library for Python. 
+Disrupt uses the [Apprise](https://github.com/caronc/apprise) notification library for Python.
 Check out their documentation for more advanced usages.
 
 Here is a small list of notification providers that Apprise supports:
@@ -49,25 +61,25 @@ Here is a small list of notification providers that Apprise supports:
 
 ## Contributing
 
-Feel free to make a feature request or if you have Python experience; pull requests are welcome 
+Feel free to make a feature request or if you have Python experience; pull requests are welcome
 too!
 
 ## Troubleshooting
 
 ### Could not connect to Docker Engine
 
-Did you mount the Docker socket to the container? Check out the [example](#usage) if you want 
+Did you mount the Docker socket to the container? Check out the [example](#usage) if you want
 to know how.
 
-In the special case that you are accessing Docker over TCP, you should place Disrupt in the 
-same network as your TCP socket. Using a Docker socket proxy (like 
-[docker-socket-proxy](https://hub.docker.com/r/tecnativa/docker-socket-proxy/), or 
-[sockguard](https://github.com/buildkite/sockguard)) is recommended for enhanced security 
-in this case. You could then configure the proxy to only allow `GET` requests for service info, 
-for example. That way, if the Disrupt container gets compromised it can't do any harm to the 
-cluster in the form of modifications/destructive instructions.  
+In the special case that you are accessing Docker over TCP, you should place Disrupt in the
+same network as your TCP socket. Using a Docker socket proxy (like
+[docker-socket-proxy](https://hub.docker.com/r/tecnativa/docker-socket-proxy/), or
+[sockguard](https://github.com/buildkite/sockguard)) is recommended for enhanced security
+in this case. You could then configure the proxy to only allow `GET` requests for service info,
+for example. That way, if the Disrupt container gets compromised it can't do any harm to the
+cluster in the form of modifications/destructive instructions.
 
-## Support 
+## Support
 
-If you're having trouble getting Disrupt to work, we have a 
+If you're having trouble getting Disrupt to work, we have a
 [Discord](https://discord.gg/tDf2yBg) for support and questions.

docker/DESCRIPTION.md

@@ -18,5 +18,17 @@
 
 # What is Disrupt?
 
-Disrupt is a Python script that will check for updates for the images of your Docker Swarm services. 
+Disrupt is a Python script that will check for updates for the images of your Docker Swarm services.
 Disrupt can either run in a container or on the host itself.
+
+## Configuration
+
+Configuration of Disrupt is done through environment variables. This is done to make the deployment of Disrupt
+environment-agnostic.
+
+Below is a list of environment variables available to be configured.
+
+| Name | Type | Options |
+| - | - | - |
+| UPDATE_DELAY | Integer | default = 300 |
+| NOTIFICATION_URL | String | Any [Apprise](https://github.com/caronc/apprise#popular-notification-services) compatible URL |