[BUG] title in browser tab doesnt changes

[nikiforovst]

Environment

Self-Hosted (Docker)

Version

2.0.8

Describe the problem

pageinfo.title does not changes title in browser tab.
This was tested on multiple systems (windows 10/ centOS 7) and different browsers (chrome/edge/IE).

Steps to reproduce:

1. Deploy new compose stack in docker as described in documentation (https://dashy.to/docs/deployment#using-docker-compose)
2. Change title (doesn matter via GUI of config files) - same behaviour - title of browser tab does not changes.

Additional info

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

Deployment | Dashy

Welcome to Dashy, so glad you're here :) Deployment is super easy, and there are several methods available depending on what type of system you're using. If you're self-hosting, then deploying with Docker (or similar container engine) is the recommended approach.

[liss-bot]

The fix for this issue has now been released in 2.0.9 ✨

If you haven't done so already, please update your instance to 2.0.9 or later. See 2.0.9 for full info.

Feel free to reach out if you need any more support. If you are enjoying Dashy, consider supporting the project.

[Techtony96]

I am having this exact issue on 2.1.1, using docker to deploy. Tested in multiple browsers.

latest: Pulling from lissy93/dashy
Digest: sha256:0bd8549e1f7157a14348a3de81d7f86babbf18583eada052af4b59e37c9e2764
Status: Image is up to date for lissy93/dashy:latest
docker.io/lissy93/dashy:latest
root@docker:~/docker/hub# docker logs -f hub 
yarn run v1.22.15
$ node server
Checking config file against schema...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Warning: 1 issue found in config file  
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. /pageInfo/navLinks must be array 
SSL Not Enabled: Public key not present

 ██████╗  █████╗ ███████╗██╗  ██╗██╗   ██╗
 ██╔══██╗██╔══██╗██╔════╝██║  ██║╚██╗ ██╔╝
 ██║  ██║███████║███████╗███████║ ╚████╔╝
 ██║  ██║██╔══██║╚════██║██╔══██║  ╚██╔╝
 ██████╔╝██║  ██║███████║██║  ██║   ██║
 ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝   ╚═╝

*******************************************************************************************
Welcome to Dashy! 🚀
Your new dashboard is now up and running with Docker
*******************************************************************************************

Using Dashy V-2.1.1. Update Check Complete
✅ Dashy is Up-to-Date

[miguelgrc]

Same issue here, also running 2.1.1

[davidfuzju]

Same issue here, also running 2.1.1

[mkhinda29]

Same issue here on 2.1.1.
I was able to get it to work by changing my docker startup command to be
command: ["yarn", "build-and-start"] as per the guidance in the developing section.

This recompiles the assets and the title lines up with what I expect.

The downside is that the yarn build adds 30+ seconds to the boot time of the dashboard.

[gdeans]

I'll try this when I get a chance. Do you need to run that command one time and then revert back?

[mkhinda29]

I'll try this when I get a chance. Do you need to run that command one time and then revert back?

If you can find a way to retain the filesystem that the dashy service is using then in theory that might work.
I am using docker compose and if I revert the startup command, it will re-create the container and it will drops the filesystem that had the build changes.

You could add a entrypoint script and manage it that way? It wasn't a big enough deal to spend any more time on ¯_(ツ)_/¯

Here is what the compose service looks like when it works if that helps. For now, I've just commented out the command: ["yarn", "build-and-start"] line and moved on.

  dashboard:
    container_name: dashboard
    image: lissy93/dashy
    command: ["yarn",  "build-and-start"]
    volumes:
      - ./conf/dashy/my-config.yml:/app/public/conf.yml
      - ./conf/dashy/item-icons:/app/public/item-icons
    ports:
      - 4000:80
    environment:
      - NODE_ENV=production
    restart: unless-stopped
    healthcheck:
      test: ['CMD', 'node', '/app/services/healthcheck']
      interval: 1m30s
      timeout: 10s
      retries: 3
      start_period: 40s