Additional pages in Dashy using docker

[PuckeyP]

Hi,
Cannot get Dashy to work with multi pages.
I'm using Dashy in a docker container - no special setup. I mount the yml config files to the app/public directory in the container and checked they are present and correct in that location

After extensive search on the internet - Github - Redit - etc, a lot of people seem to have the same problem: the pages are not showing. Even a full rebuild via the GUI does not help.

I, as many others, begin to think this is a bug in the Dashy software.
What annoys me is that any support on this subject seems to be lacking. Many questions, also about other subjects remain unanswered.

Please give us some guidance how to solve this, or, if it is an unsolved bug remove the functionality. This costs a lot of people way too much time.
PPee

[liss-bot]

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

[zmbcgn]

Hi, I am running a dashy setup within a kubernetes managed environment and have no problems with extra pages.

You know that you have to reference them in your conf.yml ? They don't appear by itself.

See: https://dashy.to/docs/pages-and-sections

What I noticed, though, is that the menu items are sometimes not "clickable", most of the time it was because of some syntax error on that subpage.

best regards

Pages and Sections | Dashy

Multi-Page Support

[PuckeyP]

Thx zmbcgn, but I did not forget to refer to the pages in the conf.yml. The pages appear in the home screen , but it does not switch to the pages when you click on it.

[CrazyWolf13]

Hi,
Cannot get Dashy to work with multi pages.
I'm using Dashy in a docker container - no special setup. I mount the yml config files to the app/public directory in the container and checked they are present and correct in that location

After extensive search on the internet - Github - Redit - etc, a lot of people seem to have the same problem: the pages are not showing. Even a full rebuild via the GUI does not help.

I, as many others, begin to think this is a bug in the Dashy software.
What annoys me is that any support on this subject seems to be lacking. Many questions, also about other subjects remain unanswered.

Please give us some guidance how to solve this, or, if it is an unsolved bug remove the functionality. This costs a lot of people way too much time.
PPee

Duplicate from #1005

[zmbcgn]

@PuckeyP Okay. That behavior I had several times, and it was most of the cases either some syntax error in the yml files (indention mistake or something similar) or I had to run an extra "yarn build" like it is suggested in #1005 .

[davros1973]

Hi - I've just started exploring Dashy and I'm also a bit of an idiot lol - but I think I'm seeing these issues too.

I'm not complaining - Dashy is exactly what I need and I think it's amazing that there is so much talent and that people provide their time and effort to make such great solutions. I thought I'd provide my Dashy-newbie perspective.

I started off with a non-customised Portainer "stack". That alone was cool! I loved it how you could quickly get going and see some results.

Then I added a volume mapping for the conf.yml and I seemed able to use the interactive editor and save to disk just fine, and see the updated conf.yml being reflected in page refreshes in different clients.

I tried adding sections and items etc. to get a feel for it.

I new I'd like tabs/pages eventually so I explored that to get a feel of it - and a basic understanding of the options; the paths and the conf.yml entries for it etc. I tried adding some with volume mappings in the Portainer Stack and by referencing them in conf.yml.

I've retried this sort of thing taking slightly different approaches or additional care ... but generally speaking it seems if I add any pages, then interactive edit no longer seems to necessarily save changes to conf.yml any more. I couldn't get any interactive edit persisting change with other (local) config yml based pages at all, and I also tried a gist based remote config yml and that didn't seem to work for me at all.

I could make other pages clickable and update their config yml manually and see the change reflected in the tabbed pages.

But ... it seems after some error condition, then that wouldn't necessarily hold true any more. It seems like some state ... some persistent state (survives container restarts) can become corrupted some how. e.g. just removing pages and page -references from conf.yml doesn't necessarily restore the ability to save to disk again from interactive edit for the main conf.yml even, even after container restart. I do have to reset essentially the non-persistent volumes too.

Always to reset, I'd end-up deleting the container (in Portainer) along with non-persistent volumes, and updating the stack (to redeploy) again ... and the the site would work again based on my conf.yml.

--
That's my perception anyway ... but as I've said, I'm often an idiot. Hopefully it's helpful.

I can make-do for now by creating sections in the main yml with reset volumes and no pages, so that I can cut and paste to other page config yml files, and re-add the pages ... but I lose the convenience of interactive edit and it's just a bit of a faff.

Still - the best dashboard software I've personally discovered, (for me), so far. Thanks! :)

-- Edit
I'm a bit tired lol - and rusty with a lot of stuff and still overwhelmed with trying to finish other stuff ... I'm likely just confused ... but Dashy seems to fit the bill of what I need so I'll download the source and try to figure out either where I'm getting confused or what's "wrong". If I can figure anything out [eventually between many demands] I'll update here or something.

-- Edit 2
I downloaded the source - following the instructions in the git readme it says to use the latest LTS version of Node which I just installed using NVM fortunately ... because then I discovered:
"node": ">=16.0.0 <18.0.0" set in package.json
Lol - might be a good idea not to say to use "latest"? :) (Makes me feel better about myself lol - that's the sort of thing I might do).

--Edit 3
So far I just set-up a folder in Windows and installed NVM for NPM & Yarn and used Visual Studio Code with useful extensions etc. I've had no problem with additional pages - just taking care to run yarn build after every change. I did notice the build process was fine with [local] folders in config.yml paths for pages, but the interactive edit yml-updates didn't seem to like additional [local] folders in the additional-page paths ... but is fine with pages in the root of the public folder. Interactive edit updated the config yml files in the public folder fine, and the build updated the dist folder with the changes just fine. I'm all in a mess at home at the moment (lots of VMs/containers in various states on multiple PC's - hence the need for Dashy lol) and I don't want to install Docker on this windows machine ... but I'll switch to a linux VM in a bit to set it up as a Dev environment and make a docker image myself and go on from there. I'm rusty with NPM and haven't used Vue before and haven't used Yarn in years ... but beginning to see how things work. I'll make sense of it eventually. :) When inspecting with devtools earlier I was seeing the error "Could not load config" or something and showing the correct route. Anyway - I'll persevere when I get time. :) I'm not terribly talented but if there's one thing I'm good at it's persevering. :)

[liss-bot]

This issue has gone 3 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[liss-bot]

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.