This Homelab Dashboard is simple and beautiful!

20 thoughts on “This Homelab Dashboard is simple and beautiful!”

• Thanks Christian, I'll just continue using Heimdal 🙂

• Is it possible to make it accessible with dashboard.local? How to do that?

• Hi Christian, thanks for the good video. I've setup Homer and after this I tried Heimdall as well. It looks a little bit cooler and as already described in other comments I prefer Heimdall too, cause editing YAML isn't that funny. And I got all the Icons for the different application types out-of-the-box. But without your video I never would have setup a Homelab dashboard. Now I have one. So thanks for the kickstart 🙂

• Homer does not support arm64 unfortunately…

• Can you do a video on how to link qBittorrent to Homer? It needs to have CORS access or something like that and I have no idea where to even begin 😂

• Very nice!
  Is it possiable to use homer dashboard kind of offline or without connection to the homer container? For example on a laptop, when you are outside of your home network?

• How do you install without docker?

• Thanks for the guide @Christian, great work.

• what about if I dont want install on Portainer but Ubunut OS?

• Awesome tool, very useful for organizing your environment, thanks!

• How to spend a lot of time to achieve a simple one page, which can be created by hands in half hour. Nice.

• HTML and Javascript, no docker needed, just the file, 1 file

• I needed to set the option AllowTcpForwarding to yes in the sshd_config and run sudo systemctl restart ssh. Maybe anyone finds this helpful 😉

• I'm now diving into dashy. Can be configured just as homer, but also in the web ui.

• There has been an update to Homer/Portainer recently and this video requires a slight revision.
  If Homer isn't launching take a look at the logs. If you get a permission error you may need to do the following.
  When adding in the env variables, do not add UID and GID, as Docker seems to handle this on its own now. Simply add the USER and GROUP and add INIT_ASSETS with a value of 0. If that still does not work, you may need to change the permissions of the file in your home directory that docker created on deployment.

• what about dashy ?

• Nice tool! I'm gonna give it a try really soon! 😉 One question: the doc doesn't give any indication on the preferred size for background image and items' logos (seems to be 64×64)… Any hint would be welcome!

• I have
  No configuration found, installing default config & assets
  Assets directory not writable. Check assets directory permissions & docker user or skip default assets install by setting the INIT_ASSETS env var to 0

• Thanks for the fantastic guide again Christian! But for the first time I am following your guides I have two questions:

  A) Why I can't dynamically assign a local Volume? Once I check the host volume I can't right, I just see a list, any idea?
  B) I am having the following errors:

  4147-08-20 07:32:16: (server.c.263) warning: clock jumped -68719476736 secs

  4147-08-20 07:32:16: (server.c.271) attempting graceful restart in < ~5 seconds, else hard restart

  1970-01-01 00:00:00: (server.c.1011) [note] graceful shutdown started

  1970-01-01 00:00:00: (server.c.2077) server stopped by UID = 1000 PID = 1

  My UID and GID are the same 1001, they I always have this error…

  Thank you very much!!

• Assets directory not writable. Check assets directory permissions & docker user or skip default assets install by setting the INIT_ASSETS env var to 0

  If anyone got stuck on that as I did, the solution is simple.
  
  When the host folder is created, it doesn't have write permission.
  
  This is the folder /home/xcad/homertest referenced in the video.

  Once you ran the container, the folder is created. On the host machine simply give it permissions like this (777 may not be the best, its a quick hack for me):
  
  sudo chmod +777 /home/xcad/homertest

Comments are closed.