Add note about how Portainer is optional

Signed-off-by: Navarr Barnier <[email protected]>

docs/services.md

@@ -3,7 +3,7 @@
 After running `den svc up` for the first time following installation, the following URLs can be used to interact with the UIs for services Warden runs globally:
 
 * [https://traefik.den.test/](https://traefik.den.test/)
-* [https://portainer.den.test/](https://portainer.den.test/)
+* [https://portainer.den.test/](https://portainer.den.test/) (Only when Portainer is enabled)
 * [https://dnsmasq.den.test/](https://dnsmasq.den.test/)
 * [https://mailhog.den.test/](https://mailhog.den.test/)
 
@@ -16,6 +16,7 @@ The following options are available (with default values indicated):
 * `TRAEFIK_LISTEN=127.0.0.1` may be set to `0.0.0.0` for example to have Traefik accept connections from other devices on the local network.
 * `WARDEN_RESTART_POLICY=always` may be set to `no` to prevent Docker from restarting these service containers or any other valid [restart policy](https://docs.docker.com/config/containers/start-containers-automatically/#use-a-restart-policy) value.
 * `WARDEN_SERVICE_DOMAIN=den.test` may be set to a domain of your choosing if so desired. Please note that this will not currently change network settings or alter `dnsmasq` configuration. Any TLD other than `test` will require DNS resolution be manually configured.
+* `DEN_SERVICE_PORTAINER=0` may be set to `1` to also run Portainer when running `den svc up`
 
 :::{warning}
 Setting ``TRAEFIK_LISTEN=0.0.0.0`` can be quite useful in some cases, but be aware that causing Traefik to listen for requests publicly poses a security risk when on public WiFi or networks otherwise outside of your control.