New NodeRed Docker build cannot edit SonosPollyTTS

General
1

Hello,
I created a docker-compose file to run NodeRed on an Intel Nuc.

################################################################################
# Node-RED Stack or Compose
################################################################################
# docker stack deploy node-red --compose-file docker-compose-node-red.yml
# docker-compose -f docker-compose-node-red.yml -p myNoderedProject up
################################################################################
version: "3.7"

services:
  node-red:
    image: nodered/node-red:latest
    environment:
      - TZ=Europe/Zurich
    command:
      - "--log.level=DEBUG"
    ports:
      - "1880:1880"
      # PollyTTS uses 1980 to setup a service
      - "1980:1980"
#    networks:
#      - node-red-net
    volumes:
      - ./data:/data
    labels:
      - "traefik.enable=true"
#      - "traefik.docker.network=traefik"

      # Define the URL to access this app
      - "traefik.http.routers.traefik.rule=Host(`nodered.${DOMAINNAME}`)"

      - "traefik.http.routers.traefik.service=api@internal"
      - "traefik.http.routers.traefik.tls.certresolver=leresolver"
      - "traefik.http.routers.traefik.entrypoints=web"
      - "traefik.http.routers.traefik.entrypoints=websecure"
      # Authentication
      - "traefik.http.routers.traefik.middlewares=usersfile@file"

#      - "traefik.http.routers.traefik.middlewares=forwardAuth"
#      - "traefik.http.routers.traefik.service=traefik"
#      - "traefik.http.services.traefik.loadbalancer.server.port=4181"

      # Global Redirect HTTP to HTTPS
#      - "traefik.http.routers.http-catchall.rule=hostregexp(`{host:.+}`)"
#      - "traefik.http.routers.http-catchall.entrypoints=websecure"
#      - "traefik.http.routers.http-catchall.middlewares=redirect-to-https"
#      - "traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https"

      # Certificate name and san
      - "traefik.http.routers.traefik.tls=true"
      - "traefik.http.routers.traefik.tls.certresolver=basic"
      - "traefik.http.routers.traefik.tls.domains[0].main=${DOMAINNAME}"
      - "traefik.http.routers.traefik.tls.domains[0].sans=*.${DOMAINNAME}"


      # - "traefik.backend=nodered1"
      # - "traefik.docker.network=web"
      # - "traefik.frontend.rule=Host:nodered.grooms.page" 

#networks:
#  node-red-net:

The service is currently running and I can access it on my local network - I have not worked on the Traefik exposure yet.

One of my first efforts was to copy some flows from an old Raspberry Pi 3 based node-red. I migrated my HueMagic flows without issue. I am now stuck trying to get SonosPollyTTS to work on the new server - it works on the old Pi.

Node install pallet

node-red-contrib-sonospollytts v1.1.23 added:
ownfile
sonospollytts
sonospollytts-config

Install the node modules inside the container:

docker exec -it d77bff0c33a6 /bin/bash
bash-5.0$ npm install node-red-contrib-sonospollytts
npm notice created a lockfile as package-lock.json. You should commit this file.
+ node-red-contrib-sonospollytts@1.1.23
added 32 packages from 83 contributors and audited 1389 packages in 7.64s

The nodes seem to have installed, but when I copy the sample node from: https://flows.nodered.org/node/node-red-contrib-sonospollytts and open the SonosPollyTTS node just imported I always see the following text rather than the configuration:

PLEASE SAVE, DEPLOY AND RE-OPEN THIS WINDOW
EVEN IF NODE-RED TELLS YOU
THAT THE NODE ISN'T CORRECTLY CONFIGURED
TO ACCESS THE CONFIGURATION

I have tried many times to get past this but no success. Is this message part of Node-Red or Part of the SonosPollyTTS add on?

Where do I go from here?

regards
Steve

2

You have mapped your local directory (./data) to the /data in the container.
You should be able to install the node outside the container, inside ./data

3

Good point, however does that not put a dependency on the host environment to have npm there too?

Don't understand how that could fix the PLEASE SAVE, DEPLOY AND RE-OPEN THIS WINDOW message though.

Steve

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.