Signal Strength App

[tonywagner]

Run it in docker somewhere on your network (like a Raspberry Pi) and then you can tune from anywhere.

https://github.com/Petelombardo/hdhomer ... /README.md

Thanks for sharing, this is fantastic! It should probably get its own stickied forum thread.

Do you plan to provide a Docker image, like through Docker Hub? If not, I would be willing.

[petelombardo]

Run it in docker somewhere on your network (like a Raspberry Pi) and then you can tune from anywhere.

https://github.com/Petelombardo/hdhomer ... /README.md

Thanks for sharing, this is fantastic! It should probably get its own stickied forum thread.

Do you plan to provide a Docker image, like through Docker Hub? If not, I would be willing.

Glad you find it useful!

I had not planned on releasing pre-built containers on dockerhub, took a quick stab at it though and I think it should be working.

Update: I published arm64 and amd64 images to Docker hub. You can access them here: https://hub.docker.com/r/petelombardo/h ... signal-web

docker-compose.yml

Code: Select all

services:
  hdhomerun-signal:
    image: petelombardo/hdhomerun-signal-web
    network_mode: host
    restart: unless-stopped
    environment:
      - NODE_ENV=production
      - PORT=3000
    volumes:
      - /etc/localtime:/etc/localtime:ro

Create the docker-compose.yml, then run it with docker-compose up -d.

[KeithAbbott]

For the Docker hub container, any chance it could be updated so that the port number can be configurable?

[petelombardo]

For the Docker hub container, any chance it could be updated so that the port number can be configurable?

The port is configurable through an environment variable at run-time. Is that not working?

If you have a reverse proxy in front (like nginx), you can setup SSL and then it is an installable PWA as well.

[KeithAbbott]

The port is configurable through an environment variable at run-time. Is that not working?

I'm using Unraid, maybe the configuration settings are different? I'm attaching a screenshot of the Update Container screen, what would I need to do to configure the appropriate environment variable?

https://drive.google.com/file/d/1iEFstb ... sp=sharing

[petelombardo]

The port is configurable through an environment variable at run-time. Is that not working?

I'm using Unraid, maybe the configuration settings are different? I'm attaching a screenshot of the Update Container screen, what would I need to do to configure the appropriate environment variable?

https://drive.google.com/file/d/1iEFstb ... sp=sharing

I haven't used Unraid, but I read "You can add, edit, or remove environment variables in the container's configuration screen through the WebGUI". When you find the spot to set an environment variable, add this: PORT=3000 -- but change the port to whatever port you want.

[KeithAbbott]

I think I'm in a catch-22. From what I can tell, Unraid will not allow you to override the port number when the container is set to host mode. If I set the container to bridge mode, I can override the port number, and I can bring up the HDHomeRun signal monitor website, but it does not find any of my devices. In bridge mode, Unraid assigns the container an IP address of 172.17.0.x, which would explain why it can't find any of my HDHomeRun devices on my 192.168.1.x subnet. Fortunately, this is not currently a major issue for me, as I am able to specify the port number for the other container that it was in conflict with.

[rikd]

I think I'm in a catch-22. From what I can tell, Unraid will not allow you to override the port number when the container is set to host mode. If I set the container to bridge mode, I can override the port number, and I can bring up the HDHomeRun signal monitor website, but it does not find any of my devices. In bridge mode, Unraid assigns the container an IP address of 172.17.0.x, which would explain why it can't find any of my HDHomeRun devices on my 192.168.1.x subnet. Fortunately, this is not currently a major issue for me, as I am able to specify the port number for the other container that it was in conflict with.

You're confusing the docker 'port' mapping with the environment variable this container uses.
To override port 3000 you need to set an environment variable called PORT
When editing the container - scroll to the bottom to ' Add another Path, Port, Variable, Label or Device'
This will open a dialog..
Set the Config Type to 'Variable'
Key should be PORT and Value whatever port number you want to use.
You can add a name, description, etc.. the main thing is the Key/Value pair
Click Add when ready and deploy your container

[KeithAbbott]

That did the trick. You sir, are a steely-eyed missile man...