[QUESTION][SOLVED] I just can't seem to get my multi-page setup to work

[coalwater]

Question

I'm trying to create a new dashy page for my frequently used links at work in a separate page, to make that my homepage in my work laptop.

I've been struggling for weeks, every now and then I keep fiddling with my conf.yml and pages, but it just never seems to work out.

I've looked into the issues and I see there's two groups of people, some who their setup just works, and some that can't get things working, and I'm starting to think it might be related to how the application is deployed.

I'm gonna share snippets here from my conf.yml and work.yml and see if you can spot something that's immediately looks wrong.

# conf.yml
pageInfo: title: My home page

appConfig:
  language: en
  startingView: default
  iconSize: medium
  routingMode: hash
  preventWriteToDisk: true
  preventLocalSave: true
  disableConfiguration: true
  disableContextMenu: true
  enableServiceWorker: false
pages:
  - name: My home page
    path: 'conf.yml'
  - name: Work
    path: 'work.yml'


sections:
  - name: Start
    widgets:
      - type: clock
        options:
          timeZone: Europe/Amsterdam
          format: en-GB
          hideDate: false
# snip

# work.yml
# copied from somewhere in the docs
sections:
- name: Work
  icon: far fa-code
  items:
    - title: Normal Item 1
    - title: Normal Item 2
    - subItems:
      - icon: si-javascript
        title: JavaScript
        url: https://developer.mozilla.org
      - icon: si-typescript
        title: TypeScript
        url: https://www.typescriptlang.org/docs
      - icon: si-svelte
        title: Svelt
        url: https://svelte.dev/docs
      - icon: si-go
        title: Go
        url: https://go.dev/doc

My current setup is deployed on a local kubernetes cluster,
the request goes through cloudflare -> firewall -> traefik (pod) -> dashy (pod)
I can verify that the work.yml file is accessible by doing curl https://mydomain.com/work.yml

If I try to click the work section on the top nav I get this error on the console

No section named 'work' was found

Which doesn't make sense because I thought dashy would be loading the full yml file, not just searching for a section called work

Another symptom that I'm not sure if it's related, it seems that the routingMode: hash is not being picked up, and dashy is still using history

Category

Configuration

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 question hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[isaaccs]

Hi, did you succeed ?

[coalwater]

I haven't had time to look deeper into this, I'll try to spend some time on it again this weekend.

[coalwater]

So I finally was able to figure out what was going wrong, I tested against the dev server using yarn dev and the pages were working just fine.

I found out that I had switched my deployment use the yarn start instead of yarn build-and-start, and when I tested with build-and-start that worked just fine.

My only question now would be, why do we need to build before starting ?

[coalwater]

I'll close this thread and open a new one concerning my question from the post above.

[kmanwar89]

I had this same issue, and was able to resolve it by performing a re-build through the GUI. Once that was done, the change of multiple pages was successfully reflected

[zbin-x]

So I finally was able to figure out what was going wrong, I tested against the dev server using yarn dev and the pages were working just fine.

I found out that I had switched my deployment use the yarn start instead of yarn build-and-start, and when I tested with build-and-start that worked just fine.

My only question now would be, why do we need to build before starting ?

docker exec -it Dashy sh
yarn build-and-start

That's it
thanks