In the conf.yml file, under the pageInfo: section, there is an attribute there called logo: and the path of the image just follows that so like: ``` logo: >- gadgeteer.co.za/wp-content/uploads/2021/12/cropped-hardhead-bevel90px.gif ```
Thank you for your video, but I would like to ask you how the raspberry pi in the upper right corner turned into a section, where should it be pageinfo and where is navlinks. I want to configure it like you do.
These are from my notes when I implemented the tabs testing so hope this will help: From github.com/Junyangz/dashy/blob/master/docs/pages-and-sections.md - Only top-level fields supported by sub-pages are pageInfo and sections. The appConfig and pages will always be inherited from your main conf.yml file. Other than that, sub-pages behave exactly the same as your default view, and can contain sections, items, widgets and page info like nav links, title and logo. Clicking on page tabs gives 'cannot GET /home/Main' error, which seems to be a path error. Bug is logged at github.com/Lissy93/dashy/issues/670 (could be resolve dby now) If the issue is that multi-pages load on click, but not on direct navigation, then: Under appConfig, set routingMode to hash. Then rebuild, and refresh the page.
Hi, many thanks for sharing this with us, can I ask if this solution has any auth based access? Basically I need to protect the dashboard with an user/pass. Many thanks!!!
I see the question also came up at github.com/Lissy93/dashy/issues/247 and the responses were given there regarding some options, and also at github.com/Lissy93/dashy/issues/64. What I do takes three clicks from outside the home, and it also gets me access to a few other LAN based services that I don't expose to the Internet. I have an OpenVPN container running. So on a mobile or other device away from home I click to open the OpenVPN app, click to activate the VPN dropping from home, then open Dashy using it's local IP address. Thing is Dashy is a bit heavy on resources depending on how much you add to it, so I did not keep it live and open while travelling away from home. At home I just use the IP address as it is all internal and behind the firewall.
Why are all dashboards in a docker container? Why can't I just install (unzip) them in my existing webserver? Why do I keep getting errors despite following the manuals? Why do all IT guys tell you it only takes a minute to setup and then make a 30 minute video? I spent almost as much time tryinh to get the dashboard to work than setting up my Proxmox server (which worked the very first time) and installing all my VMs. To me personally, it starts to feel that this dashboards is too complex to set up for what it is supposed to do. So where can I find a video that explains me what I did wrong because surely, I can't be the first and only one who's struggeling with this ?
Hi there sorry to hear it is not going well. I have tended to use Docker installations because I've found their resource requirements a lot lighter on a small server (mine is an Intel NUC), there are no clashes with other required libraries being wrong versions on the host, and updating is a lot easier (basically just recreate the container with the download of the newer image). But certainly otherwise have a look at each project eg. Dashy at github.com/Lissy93/dashy, and see what other options they provide for such as building from source in this case, or otherwise packaged executables etc. I've moved exclusively to docker containers for now though for the given reasons. Certainly a docker container install does only take a minute if the docker-compose file is correct. My videos would be way longer than that, as I tour through the menus and the settings screen to give an idea of what all can be done with. Dashy is a lot more complex though. If something quicker and easier is the object, then Heimdall I'd say is the better option to look at. Dashy requires in most cases that the YAML files must be edited and icons added manually, whilst Heimdall allows quick adding from inside it's UI.
@@GadgeteerZA Thanks so much for the reply. I'll take a look at this Heimdall, hopefully I'm more succesful in getting this to work. Not sure why I keep struggling with docker so much. I assume I'm missing some real basic understanding about the docker concept, since I seem to be quite OK with VMs and as far as I understand, the two are more or less related. It's just really frustrating being stuck on something so very simple (or so it seems when I see you guys demonstrate it).
@@arashi926 OK hope you come right. Basically you just need docker installed and then get Portainer running in a container. It is a plain start up from command line. In Portainer you can create a new stack and paste in the docker-compose.yaml text for Heimdall. That is basically the config to create Heimdall. Part of that config will be volumes to be defined. This is where the changes you make to Heimdall will be saved outside of the Heimdall container. Because when you update Heimdall, Portainer will recreate that container by pulling a fresh image. The volume ensures your changes are not lost. In that config file is also a port mapping. So when Heimdall is created, you point a browser to the IP address of the machine the container is running on, with the port address following it eg. 192.168.1.230:3567. This video at ua-cam.com/video/zVr-Eoff7Wg/v-deo.html shows how that docker-compose.yaml text is used to create a Stack inside Portainer. I watched a lot of DB Tech's videos as well as TechnoDad. I started out with a NUC box at home as a server with OpenMediaVault (OMV) running. It is easy to get Portainer going inside OMV, and then add docker containers from inside Portainer. Watch a few videos on how they paste the docker-compose.yaml files into a Stack. That was where the penny dropped for me as I started to understand how logically the config file worked. There is a left and right side to each line. Left side represents what is outside the container, and right side is what is inside.
@@GadgeteerZA I finally got Heimdal working on my Synology NAS using the default packages I can select in the GUI for docker. I'm still very confused about all the fields but I tried defaulting everything, and hey, it is working 🙂 At least I finally got started.
Great to hear. Yes take it a bit at a time. It's at least nice and quick so I use it as a dashboard on my phone too, to quickly jump to me various locally hosted services. From outside home, I just activate OpenVPN on my phone to drop into the LAN at home, and then Heimdall can quickly get me to the various services running in the home network.
hello, I'm trying to add a logo but i'm not able, how did you add your logo?
tks in advance
In the conf.yml file, under the pageInfo: section, there is an attribute there called logo: and the path of the image just follows that so like:
```
logo: >-
gadgeteer.co.za/wp-content/uploads/2021/12/cropped-hardhead-bevel90px.gif
```
Thank you for your video, but I would like to ask you how the raspberry pi in the upper right corner turned into a section, where should it be pageinfo and where is navlinks. I want to configure it like you do.
These are from my notes when I implemented the tabs testing so hope this will help:
From github.com/Junyangz/dashy/blob/master/docs/pages-and-sections.md - Only top-level fields supported by sub-pages are pageInfo and sections. The appConfig and pages will always be inherited from your main conf.yml file. Other than that, sub-pages behave exactly the same as your default view, and can contain sections, items, widgets and page info like nav links, title and logo.
Clicking on page tabs gives 'cannot GET /home/Main' error, which seems to be a path error. Bug is logged at github.com/Lissy93/dashy/issues/670 (could be resolve dby now)
If the issue is that multi-pages load on click, but not on direct navigation, then:
Under appConfig, set routingMode to hash. Then rebuild, and refresh the page.
@@GadgeteerZA I did it. Thank you very much for your help!
Hi, many thanks for sharing this with us, can I ask if this solution has any auth based access? Basically I need to protect the dashboard with an user/pass. Many thanks!!!
I see the question also came up at github.com/Lissy93/dashy/issues/247 and the responses were given there regarding some options, and also at github.com/Lissy93/dashy/issues/64. What I do takes three clicks from outside the home, and it also gets me access to a few other LAN based services that I don't expose to the Internet.
I have an OpenVPN container running. So on a mobile or other device away from home I click to open the OpenVPN app, click to activate the VPN dropping from home, then open Dashy using it's local IP address.
Thing is Dashy is a bit heavy on resources depending on how much you add to it, so I did not keep it live and open while travelling away from home. At home I just use the IP address as it is all internal and behind the firewall.
Why are all dashboards in a docker container? Why can't I just install (unzip) them in my existing webserver? Why do I keep getting errors despite following the manuals? Why do all IT guys tell you it only takes a minute to setup and then make a 30 minute video? I spent almost as much time tryinh to get the dashboard to work than setting up my Proxmox server (which worked the very first time) and installing all my VMs. To me personally, it starts to feel that this dashboards is too complex to set up for what it is supposed to do.
So where can I find a video that explains me what I did wrong because surely, I can't be the first and only one who's struggeling with this ?
Hi there sorry to hear it is not going well. I have tended to use Docker installations because I've found their resource requirements a lot lighter on a small server (mine is an Intel NUC), there are no clashes with other required libraries being wrong versions on the host, and updating is a lot easier (basically just recreate the container with the download of the newer image). But certainly otherwise have a look at each project eg. Dashy at github.com/Lissy93/dashy, and see what other options they provide for such as building from source in this case, or otherwise packaged executables etc. I've moved exclusively to docker containers for now though for the given reasons.
Certainly a docker container install does only take a minute if the docker-compose file is correct. My videos would be way longer than that, as I tour through the menus and the settings screen to give an idea of what all can be done with. Dashy is a lot more complex though. If something quicker and easier is the object, then Heimdall I'd say is the better option to look at. Dashy requires in most cases that the YAML files must be edited and icons added manually, whilst Heimdall allows quick adding from inside it's UI.
@@GadgeteerZA Thanks so much for the reply. I'll take a look at this Heimdall, hopefully I'm more succesful in getting this to work. Not sure why I keep struggling with docker so much. I assume I'm missing some real basic understanding about the docker concept, since I seem to be quite OK with VMs and as far as I understand, the two are more or less related. It's just really frustrating being stuck on something so very simple (or so it seems when I see you guys demonstrate it).
@@arashi926 OK hope you come right. Basically you just need docker installed and then get Portainer running in a container. It is a plain start up from command line. In Portainer you can create a new stack and paste in the docker-compose.yaml text for Heimdall. That is basically the config to create Heimdall. Part of that config will be volumes to be defined. This is where the changes you make to Heimdall will be saved outside of the Heimdall container. Because when you update Heimdall, Portainer will recreate that container by pulling a fresh image. The volume ensures your changes are not lost. In that config file is also a port mapping. So when Heimdall is created, you point a browser to the IP address of the machine the container is running on, with the port address following it eg. 192.168.1.230:3567.
This video at ua-cam.com/video/zVr-Eoff7Wg/v-deo.html shows how that docker-compose.yaml text is used to create a Stack inside Portainer. I watched a lot of DB Tech's videos as well as TechnoDad. I started out with a NUC box at home as a server with OpenMediaVault (OMV) running. It is easy to get Portainer going inside OMV, and then add docker containers from inside Portainer. Watch a few videos on how they paste the docker-compose.yaml files into a Stack. That was where the penny dropped for me as I started to understand how logically the config file worked. There is a left and right side to each line. Left side represents what is outside the container, and right side is what is inside.
@@GadgeteerZA I finally got Heimdal working on my Synology NAS using the default packages I can select in the GUI for docker. I'm still very confused about all the fields but I tried defaulting everything, and hey, it is working 🙂 At least I finally got started.
Great to hear. Yes take it a bit at a time. It's at least nice and quick so I use it as a dashboard on my phone too, to quickly jump to me various locally hosted services. From outside home, I just activate OpenVPN on my phone to drop into the LAN at home, and then Heimdall can quickly get me to the various services running in the home network.
This looks like something I could use. Thank you :-)
Thanks for this 👍🏻
Great video!
Thank you!
Very interesting!