docs: base path documentation update, oicd example mentioned

Author: s4s0l

.examples/docker-compose-oidc/compose.yml

@@ -1,3 +1,8 @@
+# Note that this example is using network_mode: host, which may have security implications.
+# It is done this way for simplicity, to avoid complications that come from the fact that 
+# Gatus NEEDS to see authentication provider under same address as the one used by the end-user.
+# This way both Gatus and the end-user see the authentication provider under "localhost", what 
+# is convenient for local testing.
 services:
   dex:
     network_mode: host

.examples/docker-compose-reverse-proxy-oicd/compose.yml

@@ -1,4 +1,8 @@
-
+# Note that this example is using network_mode: host, which may have security implications.
+# It is done this way for simplicity, to avoid complications that come from the fact that 
+# Gatus NEEDS to see authentication provider under same address as the one used by the end-user.
+# This way both Gatus and the end-user see the authentication provider under "localhost", what 
+# is convenient for local testing.
 services:
   dex:
     network_mode: host

README.md

@@ -2666,6 +2666,8 @@ security:
 
 Confused? Read [Securing Gatus with OIDC using Auth0](https://twin.sh/articles/56/securing-gatus-with-oidc-using-auth0).
 
+The example configuration using [Dex](https://dexidp.io/) as the OIDC provider, 
+can be found in [.examples/docker-compose-oidc](.examples/docker-compose-oidc).
 
 ### TLS Encryption
 Gatus supports basic encryption with TLS. To enable this, certificate files in PEM format have to be provided.
@@ -3272,10 +3274,17 @@ clears their browser's localstorage.
 
 
 ### Exposing Gatus on a custom path
-Currently, you can expose the Gatus UI using a fully qualified domain name (FQDN) such as `status.example.org`. However, it does not support path-based routing, which means you cannot expose it through a URL like `example.org/status/`.
+Gatus always exposes its endpoints and UI under the root path ('/'), and it cannot be changed.
+However, if you find yourself in a situation where you need to expose Gatus on a custom path (e.g. `/gatus/`),
+you can achieve this by using a reverse proxy such as Nginx or Traefik or Caddy to handle the path rewriting for you.
+In order for it to work properly, you must tell Gatus to use the custom path as its `web.base-path` so that all links
+are generated correctly and redirections work as expected.
 
-For more information, see https://github.com/TwiN/gatus/issues/88.
+See [examples/docker-compose-reverse-proxy](.examples/docker-compose-reverse-proxy) for example using Caddy.
 
+Note that if you are using OIDC for authentication, your `security.oidc.redirect-url` must include the custom path as well.
+
+See [examples/docker-compose-reverse-proxy-oidc](.examples/docker-compose-reverse-proxy-oidc) for an example using Caddy and OIDC.
 
 ### Exposing Gatus on a custom port
 By default, Gatus is exposed on port `8080`, but you may specify a different port by setting the `web.port` parameter: