diff --git a/404.html b/404.html index 6922efc..05c07c6 100644 --- a/404.html +++ b/404.html @@ -10,7 +10,7 @@ - + @@ -18,10 +18,10 @@ - + - + @@ -352,6 +352,19 @@ + + + + + + +
  • + + Metrics + +
    • + + @@ -366,10 +379,6 @@

    404 - Not found

    - - - - @@ -394,8 +403,8 @@ - - + + - + + - + + - + + - + + - + + - + + - + + + + + + + + + \ No newline at end of file diff --git a/notifications/index.html b/notifications/index.html index 5ae5e6e..0ae2965 100644 --- a/notifications/index.html +++ b/notifications/index.html @@ -12,7 +12,7 @@ - + @@ -20,10 +20,10 @@ - + - + @@ -445,6 +445,19 @@ + + + + + + +
  • + + Metrics + +
    • + + @@ -553,13 +566,13 @@ The types of notifications to send are set by passing a comma-separated list of

    There is currently a bug in Viper, which prevents comma-separated slices to be used when using the environment variable. A workaround is available where we instead put quotes around the environment variable value and replace the commas with spaces, as WATCHTOWER_NOTIFICATIONS="slack msteams"

    -

    If you're a docker-compose user, make sure to specify environment variables' values in your .yml file without double quotes (").

    +

    If you're a docker-compose user, make sure to specify environment variables' values in your .yml file without double quotes (").

    This prevents unexpected errors when watchtower starts.

    Settings

    Available services

    Email

    @@ -583,7 +596,7 @@ The types of notifications to send are set by passing a comma-separated list of -e WATCHTOWER_NOTIFICATION_EMAIL_FROM=fromaddress@gmail.com \ -e WATCHTOWER_NOTIFICATION_EMAIL_TO=toaddress@gmail.com \ -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp.gmail.com \ - -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587 \ + -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587 \ -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=fromaddress@gmail.com \ -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=app_password \ -e WATCHTOWER_NOTIFICATION_EMAIL_DELAY=2 \ @@ -591,16 +604,16 @@ The types of notifications to send are set by passing a comma-separated list of

    The previous example assumes, that you already have an SMTP server up and running you can connect to. If you don't or you want to bring up watchtower with your own simple SMTP relay the following docker-compose.yml might be a good start for you.

    -

    The following example assumes, that your domain is called your-domain.com and that you are going to use a certificate valid for smtp.your-domain.com. This hostname has to be used as WATCHTOWER_NOTIFICATION_EMAIL_SERVER otherwise the TLS connection is going to fail with Failed to send notification email or connect: connection refused. We also have to add a network for this setup in order to add an alias to it. If you also want to enable DKIM or other features on the SMTP server, you will find more information at freinet/postfix-relay.

    +

    The following example assumes, that your domain is called your-domain.com and that you are going to use a certificate valid for smtp.your-domain.com. This hostname has to be used as WATCHTOWER_NOTIFICATION_EMAIL_SERVER otherwise the TLS connection is going to fail with Failed to send notification email or connect: connection refused. We also have to add a network for this setup in order to add an alias to it. If you also want to enable DKIM or other features on the SMTP server, you will find more information at freinet/postfix-relay.

    Example including an SMTP relay:

    ---
-version: "3.8"
+version: '3.8'
 services:
   watchtower:
     image: containrrr/watchtower:latest
     container_name: watchtower
     environment:
-      WATCHTOWER_MONITOR_ONLY: "true"
+      WATCHTOWER_MONITOR_ONLY: 'true'
       WATCHTOWER_NOTIFICATIONS: email
       WATCHTOWER_NOTIFICATION_EMAIL_FROM: from-address@your-domain.com
       WATCHTOWER_NOTIFICATION_EMAIL_TO: to-address@your-domain.com
@@ -622,9 +635,9 @@ The types of notifications to send are set by passing a comma-separated list of
       - 25
     environment:
       MAILNAME: somename.your-domain.com
-      TLS_KEY: "/etc/ssl/domains/your-domain.com/your-domain.com.key"
-      TLS_CRT: "/etc/ssl/domains/your-domain.com/your-domain.com.crt"
-      TLS_CA: "/etc/ssl/domains/your-domain.com/intermediate.crt"
+      TLS_KEY: '/etc/ssl/domains/your-domain.com/your-domain.com.key'
+      TLS_CRT: '/etc/ssl/domains/your-domain.com/your-domain.com.crt'
+      TLS_CA: '/etc/ssl/domains/your-domain.com/intermediate.crt'
     volumes:
       - /etc/ssl/domains/your-domain.com/:/etc/ssl/domains/your-domain.com/:ro
     networks:
@@ -687,7 +700,7 @@ The types of notifications to send are set by passing a comma-separated list of

    -e WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN or --notification-gotify-token can also reference a file, in which case the contents of the file are used.

    -

    If you want to disable TLS verification for the Gotify instance, you can use either -e WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY=true or --notification-gotify-tls-skip-verify.

    +

    If you want to disable TLS verification for the Gotify instance, you can use either -e WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY=true or --notification-gotify-tls-skip-verify.

    containrrr/shoutrrr

    To send notifications via shoutrrr, the following command-line options, or their corresponding environment variables, can be set: