Returned here after a few failed attempts to correct some configurations. Listened to the whole video, and finally understood about Docker errors when creating directory structure on the host! Thanks!!
I've noticed a few times you make a 'docker-run.txt' file that you then 'cat' and copy and paste into the shell. A shortcut would be to just run it with your shell, for example '/bin/sh docker-run.txt' will treat it as a shell script and execute the command(s) inside. You could also mark it executable and put a shebang in it like a normal shell script so you can invoke it directly. Cheers, and thanks for all the great content.
Great tip! Thanks for that!. I have started just turning everything into docker-compsoe files lately, as the tooling is really great for doing fast updates and bring the system down and up easily.
Video is fairly old but if you haven't already I'd suggest switching to docker compose files. Much easier to bring containers up and down and make changed/update.
A couple of things to note on this, when you copy and paste the code from open source is awesome wiki it gives ports as 8295:80 in the vid Brian states don't change the right port i.e 80 and leave as is, it looks like dashy now uses port 8080, which is great news for those hosting other services on port 80, another thing id say to beginners like me, is reboot after install just to make sure that everything is going to work, you don't want to get to widgets etc for your whole site to be blocked, there probably is no need but forwarding ports may alleviate some connection issues.
Didn't realize it used 8080 internally now, but thanks for the tip. The port forwarding, if you are exposing it externally, should really be done through a reverse proxy, and protected with an ACL of some sort as well.
Thanks for this Brian, it gave me the nudge to use dashy rather than just Heimdall. Just a quick note, it may be worth mentioning that yaml files have a very specific structure which if you mess up can cause things to break. (Guess Who broke his 😂)
Thanks for the video, Dashy is the first thing I wanted to make in docker assuming it would be less advanced. This video does a great job of explaining docker in general, now I have a grasp and can move forward. Also somehow I screwed up exporting a dashy config for a base config any time I was referencing to it, dashy would just load a dark blue background. Wasn't until this video that I could rule everything but the config out as a possible cause. Used the example config you provided and it worked like a charm.
Yes, but while Dashy and Heimdall are too simple for my purpose. But Organizr has just too much options. Heimdall was already one of my Favs but i went with b4bz Homer dashboard
@@DigitEgal I always say use what works best for you. That's the wonderful thing about open source. There are so many options, and slightly different takes to the extremely different ends of the spectrum for applications trying to solve the same problem.
Sometimes if the status icon is red it could be an expired SSL certificate. In that case you can add a status check url with instead of the normal . This fixed some of my issues.
Yes, apologies, I just moved everything to a new site, and now have to go update links. If you just go to shownotes.opensourceisawesome.com and use the search you should be able to find the articles.
Here's a tip: If you want to mount a subfolder in the same directory as the docker-compose.yml, you can use a relative path on the left of the colon. Example: "./public/conf.yml:/app/public/conf.yml" This works great when you are composing from inside the projects directory.
Great tip! I do use this on a lot of my projects. I think there was an issue with the relative paths with a certain version of compose...for some reason it gave me trouble, but in the last yea, this has been what I do as well.
Hi Brian love your videos.... What I still don't understand. Some containers needs port 80....like NPM. And for instance this container also.... Some containers don't. Like changing ports.... What to do when there is a conflict?
In docker, you use Port mapping (like port forwarding in a router) to map a port on the host that's free, to a port on the container. Essentially the port mapping will look like this 80:80, where the left side is the host port, and the right is the container port. You can change the left side to any port that is free on your host machine. Just don't change the right side. by doing this, you remove those conflicts.
Hello Brian, I am a newbie in docker and want to thank you for your excellent video's. They have been a great help for me. I would like to subscribe to your shownotes but the link doesn't seem to work. Thanks again and greetings from the Netherlands!
Yeah, not sure I ever setup email on my blog. I just link to them from the videos. But I’ll take a look this week and see if I can get the blog subscriptions working. Thanks for letting me know.
I really like homer, and I really like Dashy as well. I'm all about having options, and when it comes to dashboards, there are plenty of amazing, open source, options out there.
I got it working and it was easy enough. Adding the images is not wokring though. Tried doing it with local images and also with the images uploaded to the internet
Love this video, one question, under Edit Section>Section Icon>fas fa-server. Is there a list of icons I can view to add? Example how did you know to type in fas fa-server?
When you launch Dashy, I noticed you get a different IP compared to the IP of your Portainer host. But for me, I get the same IP as my portainer host just on a different port. How do I make it so I get a unique IP on my hosts network rather than dockers internal network which makes my portainer host act like a gateway/router?
I get the different IP because I run Dashy on a different VM. I actually run my NGinX Proxy Manager, Portainer, and a few other core services (Pihole, and backup Pi-Hole each on their own LXC containers) on an LXC container in Proxmox because LXC reboots so much more quickly than a regular VM. Dashy is running on my Ubuntu VM, so it (to my network) appears as a different machine. So to answer your question, you'd want to setup a couple of LXC containers then install docker on them, or run a couple of VMs with docker installed, but you'd still get multiple apps with the same IP. The same IP is really a benefit to using docker. Use the port mapping in docker to your advantage, and save yourself some resources.
The volume mappings allow you to define where you want the data persisted on the host system. The left side of the mapping is where you can choose where the data will be stored. - /home/brian/docker/dashy:/config Tells you that the path /config in the container is persisted on the host machine at /home/brian/docker/dashy Does that help?
I'm not sure on Synology, but I would guess you can setup a space to create volume mappings in Synology as well. This link www.wundertech.net/how-to-use-docker-on-a-synology-nas/ appears to have some information that may help.
Hello Brain, All of the proxy urls with FQDN is showing as ENOTFOUND -3008 in dashy, like the one you showed in this video for Homeassistant. Any idea on how to correct this issue ?
Would depend on whether your server can route to the FQDN with something like traceroute, or simple ping. If so, then there may be something else causing an issue with routing.
@@AwesomeOpenSource Thanks Brain, i solved the issue by changing the status check url, disabling the SSL check and finally accepting error codes related to authorizations
I'd have to know how you've setup your volumes and such inside Dashy. You can jump over to discuss.opensourceisawesome.com and ask in the #help-me-please channel. Someone will help out, if not me specifically.
Not that I'm aware of. I think you'd have to have the hooks to call the xdg-open function of the browser...and I'm just not sure how to do that. I suppose you could link to the file on the file system and see if it prompts you to open it in the right application. Just not sure how efficient that would be.
On the right end of the UI, there is a wrench icon, a pencil icon, and a few others. The pencil will put you into edit mode on the UI, and from there you can add groups and widgets.
@@AwesomeOpenSource I found that part and can add items but don't see how to make the item a widget vs a hosted service/server like Plex or Proxmox etc.
Hello there: What is the way to update dashy ? I tried to recreate the container from within ooersoner but it still sat that it is on Version 1.9.9 and needs 2.0.3 Is there a special way to update it to the newest version ?
If you're running it with docker-compose, then go into the folder where you docker-compose file is, and do the command docker-compose pull Next, do the command docker-compose up -d And the newly pulled version should get up and running.
Homer vs Heimdall vs Dashy. Any else? For me: Heimdall is the easiest. But somehow, sometimes it's stop working, logo not open, etc. But, instead of yaml file, Heimdall is easiest. Dashy, it's Heaviest of the three. I thought I'll try homer, but I'm not succeed even once to get it up and running. On January 2023, Homer installation is a headache.
Dashy has a nice Web UI for configuring the pages once you've got the core system setup. I've not noticed it's heavy. Homer hadn't gotten updates in a long while, and Heimdall either, so not sure if they've been updated lately. There are tons of home pages. I think one is called "Homepage". You might also check out Flame, and Organizr.
I believe that’s all I did. I just stopped the container and removed it, this should leave you mapped volumes alone, updated the config, and re-ran the Docker run command.
there are quite a few visual bookmarking apps in open source, but I've never used Rainloop, so not sure how any would compare to features. Can you tell me more specifically what you might want out of an open source option?
@@AwesomeOpenSource If I add youtube videos in it, it needs to add also the description and be able to search that also not only the title, the ability to tag videos based on themes, interests.
Dashy is compareable to Heimdall or b4bz Homer or even Organizr. While Guacamole is more compareable to Teamviewer or even Shells / Parallels / Teleport.
@@DigitEgal Got it, didn't see the complete video, so directly jumped on conclusions. I have worked on Guacamole, so pretty much know about its working.
do yourself a favour... whoever you are... just skip this mess of a system i have literally managed to succesfully display 1 icon after 4 hours.... complete waste of time! not even supported by its creators it seems
It's still supported. The Github page shows updates just yesterday, 3 days ago, last week, and so on. I'm sorry you have issues getting it setup. This video is getting a bit old, so may my steps aren't as accurate anymore.
just wondering ...i followed the tutorial however i am unable to get the icons to show "icons/dashboard-icons/png/proxmox.png" i do however see it my docker folder on my host...and i can see the many icons there....any thoughts on what i might have done wrongly? When i checked portainer i can see the volumes listed there: /home/shawn/docker/dashy/public/conf.yml /app/public/conf.yml /home/shawn/docker/dashy/icons /app/public/items-icons/icons
So, depending on your browser, you may need to turn off caching, or disable caching for a refresh. With firefox, I usually have to close it completely, then re-open it to get it to clear the cache for the icons to show. Sometimes using CTRL + F5 works, or CTRL + R, etc...but usually just close and re-open it.
@@AwesomeOpenSource tried to close everything ...cleared the cache plus ctrl+f5 none of it seems to work for some reason. i can edit the conf.yml and i know that is updating properly
@@AwesomeOpenSource ""/home/shawn/docker/dashy/icons/dashboard-icons/"' and within this folder is where PNG and SVG folders are... thank you so much for taking the time
Your inability to get something to work doesn’t constitute a waste of time forr others. If you’ll let me know what went wrong, any error you saw or issue you had and on which step, I’m happy to try and see if something has changed.
