Closed benphelps closed 1 year ago
I'm being thick. Can anyone give an example of where to put the code to implement the five columns option? and bonus points if you can paste a screenshot of the five columns in action.
In the kubernetes integration, could we change the status (e.g. RUNNING
) to a dot like the Docker integration? Looks slicker imo.
It could also be a flag in kubernetes.yaml
?
Also is there a way to control where the homepage "card" goes? It automagically appeared when I enabled Kubernetes integration but it has its own column. I'd like to move it somewhere else tidier. (I might have missed something in the doc though)
what am i getting wrong here?
i want the 'RPIs' column to appear before the 'Usenet' and 'Hubs' column
my yaml looks like this, but no matter how many times i adjust it and save it the columns won't switch...
First time this hasn't worked for me. What am I getting wrong?
I'm being thick. Can anyone give an example of where to put the code to implement the five columns option? and bonus points if you can paste a screenshot of the five columns in action.
ignore this, of course i forgot you have to amend the settings.yaml rather than just move stuff around in services. because i'm a cretin.
Might be neat if an entry with associated widget enabled had the same height as two normal entries. You know, to keep things aligned nicely. Couple of pixels off at the moment.
If mb-3
was changed to mb-2
that should be margin-bottom: .5rem
(instead of margin-bottom: .75rem
) then we would get the trick to accomplish this alignment...
I'll search the way to make this change and put a PR, but I can't promise anything...
Might be neat if an entry with associated widget enabled had the same height as two normal entries. You know, to keep things aligned nicely. Couple of pixels off at the moment.
I'll search the way to make this change and put a PR, but I can't promise anything...
Recently some Dashboard icons were updated, and some of the more narrow/taller icons are throwing off the layout. Is there a way to set a max height to force consistency? (Firewalla & Portainer examples below)
Recently some Dashboard icons were updated, and some of the more narrow/taller icons are throwing off the layout. Is there a way to set a max height to force consistency? (Firewalla & Portainer examples below)
It should be solved in next release thanks to this PR: https://github.com/benphelps/homepage/pull/1405...
Is anyone having an issue where the icons in the bookmarks are vertically misaligned? I use dashboard icons.
This does not happen with mdi-icons
I noticed all my bookmark icons shifted down a few px as well. It seems as long as I'm not using mdi-icons, both dashboard icons and custom icon will have this mis-align issue.
I have been having layout issues mostly due to some widgets requiring two rows for the names of the fields within them and others just one. It would be nice if one could adjust the names of the fields independently of the translation. That way one could shorten fields as needed rather than being tied to the existing translations. I would assume that this should be possible to implement through the existing translation engine comparatively easily?
My layout keeps reverting back to columns even when my settings.yaml indicate rows. If I just open the file and resave it, it will revert back to rows. Here is my settings.yaml file (renamed to txt so I could upload). I've also attached 2 files showing the difference. settings.txt
Came here to report this as well. It keeps happening.
Same issue here after updating to v0.6.19 (be7aa58, May 17, 2023). Never had the issue before updating. Have to hit the 'refresh' button on the page to get it to reset.
Need anyway to load custom CSS and JS.
A unified layout scheme for services, widgets and bookmarks may be the more flexible way to go. Adding widgets to a service may increase the height of the service component, it would save a lot of screen space if there was a dynamic layout method that could fill the gaps to the left and right of the tall component.
This is no longer useful as a megathread. Feature requests can be opened in discussions, bugs as issues. Thanks all.
This issue will serve as a single point of discussion for anything related to layout or positioning issues, bugs, suggestions, etc.