Mattaton

Had to stop using luckyBackup as it appears to change the owner of directories. I run immich on my server and I had luckyBackup syncing the photos to another server. But intermittently, I'd have photo auto-backup from the app fail and I'd find that all the directories in the immich folder had the owner changed to UNKNOWN. I'd chown the owner back to nobody and auto-backup would start working again. Then a couple days later I'd realize photo backups weren't working again and sure enough the owner was switched back to UNKNOWN again. So, given that luckyBackup had direct access to the share, it seemed like the obvious culprit. So I looked at other folders that luckyBackup was backing up and sure enough, all the owners were set to UNKNOWN. In those cases it wasn't breaking anything because what it was backing up was already in a backup folder on the local server and LB was only syncing those backups to another server. With Immich, it was affecting the live folder. Is this a known issue?

@D34DC3N73R Reading through the last few posts on this page and got netdata up and running again with your new template. Thanks for the great instructions! I could not figure out how to get the official template to see my GPU. Will your template end up on the CA Apps (replacing the glibc one) or will it always just be manual download? Thanks!

Might be possible with custom CSS, but given we're dealing with a table, it could be difficult to pull off. Hiding the entire column is easy, but only hiding the column in compressed rows is tricky since the column is persistent through compressed and expanded rows. Kinda all or nothing.

I went ahead and posted an issue on the Github. This may be normal behavior, but I figure we can flag it just in case. https://github.com/imagegenius/docker-immich/issues/415

I'm having the same issue. Usually have to stop it and restart and then it'll fire up. Actually just yesterday after updating the container it did this and I was drafting a message on the Discord server about it, then it suddenly started as the log window started filling up with the usual start up lines. So it appears it does eventually start of you leave it long enough. But it starts more normally if I stop it and restart it just after updating. I don't know if there's another batch of processes starting that doesn't log to this screen or what, but I do think it's something that should be looked into. An issue posted on the imagegenius GitHub is probably in order.

Nice. Glad you guys got it going! Enjoy!

@mbc0 So, it looks like you have made the GPU available to the container, but you also need to turn on GPU acceleration in the Immich settings. Also, imagegenius recently changed how the AIO container uses the GPU. They now maintain 4 versions of the container depending on your scenario: https://github.com/imagegenius/docker-immich/issues/392 You'll no longer use the MACHINE_LEARNING_GPU_ACCELERATION varaiable and instead set the version tag to :cuda instead of :latest

Is there a way to prevent this from happening? Some items run right into the edge of the browser window. Can we add a padding around the entire interface just to give a little breathing room? Thanks!

Nice! Since we have now moved the ability to disable the image saturation to the vars file for easy access, I think I should probably move the rules for the container image into the organized grouping/flow of the CSS file instead of having it at the very top. More like how the rules are for the folder icon/image (that you show above) are organized with other rules for that area.

Excellent. I updated all three themes on the repo with these changes.

HAHA! Awesome! I just changed mine to do that as well. Removed the height/width rules. Works great. I'll update the repo to use that method. Much better.

Cool. Yeah, with the transform/transition approach, you can probably just ditch the width/height rules. Then you can just make the value for --container-logo-size-hov be 1.2 and assign that to your scale function in the transform rule instead of setting the scale in the rule itself. Not a bad way to tackle that! Nice job!

Yeah, that's just a side-effect of the image growing. The image is taking more horizontal space, so everything to the right has to shift as it changes. That's the main reason I don't use the size change on hover. Just too much movement and shifting as the cursor moves around the screen. To stop that from happening would take a lot more CSS rules and possibly even changes to the html.

Thanks! Let me know if you see anything else or think we should tweak anything. Once we get it all sorted I'll update the other themes to match.

Yes. Shame on me for committing changes to the repo without fully testing. 🙂

I would not do it this way. It may work fine, but it also may have some unforeseen effects in changing the regular size variable to be the same value as the hover size. Better to use them separately, in my opinion.

Had a typo and needed to add !important to overcome higher-specificity rule later in the code. width: var(--container-logo-size-hov) !important; /* important needed to overcome higher-specificity selector rule below */ height: var(--container-logo-size-hov) !important; /* important needed to overcome higher-specificity selector rule below */

I suppose this would work. Redefining the variable's value in the selector. What I would do to keep things organized is create a new variable alongside the --container-logo-size with the rest of variable definitions. Something like --container-logo-size-hover and then set the hover size you want there. Then a width/height rule should be in the selector with its value set to the new variable. I've updated the github code for the urblack-theme to add variables for icon hover size and both initial saturation and hover saturation. Added this to the 02-vars.docker.css file: --container-logo-size-hov: 38px; --container-logo-saturation: 0; /* Initial color depth for container icons - 0 is fully-desaturated (grayscale), 1 is default saturation */ --container-logo-saturation-hov: 1; /* 1 is 100% or default color depth - Values above 1 will saturate beyond default colors, Example: 4 = 400% */ Changed the saturation rules at the top of 04-table.docker.css (not just for saturation anymore): /*************************************************/ /* CONTAINER LOGO ICON HOVER EFFECTS */ /*************************************************/ .folder-preview-wrapper img { /* Desaturate docker container icons */ filter: saturate(var(--container-logo-saturation)); } .folder-preview-wrapper:hover img { /* Saturate docker container icons - Values above 1 will further saturate */ filter: saturate(var(--container-logo-saturation-hov)); /* Set the hover size for icons */ width: var(--container-logo-size-hover); height: var(--container-logo-size-hover); } With these changes, icon saturation and size should now only be altered by changing the variable definitions in 02-vars.docker.css, and not the rules in 04-table.docker.css This makes it easier for folks who don't want to or have the knowledge to dig into the CSS selectors and rules. Just change the variable values and it will take effect. I'll update the other 2 color themes soon. But the changes above can easily be copied into the files you already have in place on your system. P.S.: I don't know if it's just me, but the CSS color scheme for code here on the unRAID forums is horrible to read against the dark gray background of Dark Mode. The red comments especially are very hard to read.

That really is a completely subjective thing. With something like this, it's all about what YOU want to see. I think it's fine. Might even try it myself. 😄

Monsoon level. Get your umbrella ready. 😄

Hmmmm...yeah you should be able to comment out the whole block (both rules) and have it revert to default state (saturated). It may have just been your browser caching the desaturate CSS. CTRL+F5 will refresh and grab updated files and clear up stuff like that more often than not. But what you did will definitely work, it's just redundant. "Please fully saturate this fully-saturated icon." 😄 Just FYI: The 0 is not really for false, it's more of a percentage. saturate(0) is 0%, saturate(1) is 100%. Using decimals between 0 and 1, you can get granular with it. If you REALLY like color, you can super-saturate by going over 1. Like saturate(4) if you're feeling crazy. 😄 Ant any rate, I'm glad you got it sorted!

Mine does, but be warned the graph area was very hard to target the size and keep it contained. It does some funky things, even on the vanilla version when the page is resized. I never could nail down a way to control it without breaking it. Such is the nature of trying to overcome built in styles with custom ones. Otherwise, the rest of the pop up is fully styled and customizable. If you go to my GitHub page, there's some documentation and more documentation in the form of comments in the css files themselves. I have several styles to go along with the built in unRAID themes. I also have a whole slew of commented variables in the heads of the css files where you can tweak lots of things without having to dig into the styles directly on your own. Once again, more info on the GitHub page Also @Masterwishxstarted with the styles I did and further customized. Have fun and enjoy! 😊

I have custom CSS available. It has a lot of options in it, one of which is to change the play/stop icons based on autostart status. See the readme on the repo for more info: https://github.com/Tyree/folder.view.custom.css

Yeah that would be difficult. I mean, I guess you could edit the file that contains the order and ignore the icon being red. But the next time you changed the order on the docker page it would overwrite the file. I wouldn't if I were you. 😄

You can unlock the folder order (padlock icon at the top) on the Docker page to reoder the folders. Within a folder's settings screen (click on a folder name to reach the settings screen), you can drag and drop to reorder the containers within the folder. On the Docker page, after you change the order, the pentagon-shaped icon at the top may turn red indicating the order you see on the screen does not match the order for Dockerman (unRAID). To fix this, unlock the order on the Docker page, change the order of anything. Lock it. Unlock again, move the item back where desired, and relock. Refresh the page and the icon should be green.