fix: correct real-world deployment details found while writing the stacks entry

- docker-compose.yml used "websecure" as the entrypoint name; the
  actual falcon_network convention (confirmed against the real
  traefik/compose.yml) is "web-secure". Also switched the networks
  block from a hardcoded falcon_network to the same
  compose_network-aliased ${NETWORK_NAME} pattern already used in the
  Traefik labels, instead of only half-respecting that variable.
- config.yml gave the Traefik widget an href, but this deployment runs
  with --api.dashboard=false - there's no dashboard to link to.

docker-compose.yml

@@ -24,7 +24,7 @@ services:
       - ./config:/app/config:ro
     env_file: .env
     networks:
-      - falcon_network
+      - compose_network
     labels:
       - traefik.enable=true
       - traefik.docker.network=${NETWORK_NAME}
@@ -33,11 +33,8 @@ services:
       - traefik.http.routers.pulsenode-web.entrypoints=web
       - traefik.http.routers.pulsenode-web.middlewares=pulsenode-redirect-web-secure
       - traefik.http.routers.pulsenode-web-secure.rule=Host(`${TRAEFIK_HOST}`)
-      - traefik.http.routers.pulsenode-web-secure.entrypoints=websecure
+      - traefik.http.routers.pulsenode-web-secure.entrypoints=web-secure
       - traefik.http.routers.pulsenode-web-secure.tls.certresolver=resolver
-      # Verify these entrypoint/middleware/certresolver names against
-      # traefik/dynamic/*.yaml in the stacks repo before deploying - written
-      # to match that repo's own convention, not independently confirmed.
       - traefik.http.routers.pulsenode-web-secure.middlewares=security-headers@file,no-index@file
       - traefik.http.services.pulsenode-web-secure.loadbalancer.server.port=3000
     healthcheck:
@@ -48,5 +45,6 @@ services:
       retries: 3
 
 networks:
-  falcon_network:
+  compose_network:
+    name: ${NETWORK_NAME}
     external: true