Mattaton

I've been able to access shares no problem until I set the Flash to be accessible (so I could access a plugin while developing some custom CSS). I set it to Private and gave my smb user r/w access, and now ALL shares are inaccessible. Even the ones that were set to share-public. I've gone as far as rebooting the server, creating a new user and granting it access. Nothing works. I'm on Windows on a domain. So when I try to access the server, Windows automatically sets the user as being on the domain AP\user in my case. Which doesn't work. Not surprising. So I change the user to be apunraid\user whereas apunraid is the name of the server. Still doesn't work. I've attached my diagnostics. Can anyone help? Thanks! apunraid-diagnostics-20230925-0757.zip

@Squid Sorry for the delay. I tried deleting the container again and then immediately exported the diagnostics. Thanks! tyreemedia-diagnostics-20230925-0712.zip

I'm not sure how it's used elsewhere in unRAID, so I don't know if this breaks something or not. This is still the toolstipster, though. Like I said, that is the element with the border, so there's no real way to get around styling it for the border (and shadow)... But, you can style the .preview-outbox for your padding and background color. Sorry, I had some other things to get done today, so I'm not focused on this at the moment. I'll look back at what you've accomplished later tonight.

Check out the code near the bottom of this where I was styling the advanced context window for a dark mode. It has basically everything pulled into a selector you can play with. It's commented so you can see what's what. https://github.com/Tyree/folder.view.custom.css/blob/context-menu-dark-mode/docker-custom.css Although I did style the root tipster element, against @scolcipitato's advice. That's what has the border styles on it, so I'm not sure how else to affect/override the border without styling that element.

Agreed. I, personally, rarely use the dashboard for anything and pretty much always go straight to the docker tab if I'm in unRAID for that reason. When I start unRAID it's on the Main tab, so it's one click to go to Dashboard or Docker. Easy choice. 🙂

Strange. Mine doesn't look like yours. Top and bottom space looks pretty even on mine:

I appreciate it, but I am just hacking my way through it. A real CSS programmer would probably cry over the BS I'm slingin' 😄 My comments inline below... Yeah, I think @scolcipitato has to add those in before I can style them or give an option to show/hide them. Can do. I'll see what I can do. Some of this is a min-width based on how long a container name MAY be. Looks odd when the names are short, but could be troublesome if the names are long. But yeah, I'll see what I can do. This should be doable. I think I can also affect just the container icons or the folder icons. Give separate controls. Hmmmm...this would involve @scolcipitato again. Making the down arrow close the folder will be somewhat impossible since they don't "exist" in the html code. I am adding it with CSS. So scolcipitato can't make that any sort of event handler for closing the folder. He can have the folder icon just open and close with a left-click, but what about all the other options in the context menu?

I started a new branch for the advanced context menu dark mode. https://github.com/Tyree/folder.view.custom.css/blob/context-menu-dark-mode/docker-custom.css All the styles at the top are the same as my other custom CSS file, but at the bottom you'll find all the dark mode styles. I set out a bunch of variables so that folks can take this boilerplate and change colors as they see fit without having to dig too deep into the CSS selectors themselves. As I'm sure there will be, let me know if you have any issues as not everyone has the same unRAID theme, I very well may have missed something.

@scolcipitatoI'm currently working on a dark mode style for the advanced context window and I'm noticing the graph at the top for cpu usage doesn't seem to do anything. I'm assuming the span within the div.usage-disk is supposed to change its width based on the cpu usage percentage, but its width stays at 0%.

New custom CSS update added a few variables to control autostart icon size independently from normal icon size. Also variables for icon and color of spin icon started versus stopped. I may work on a dark theme for the context menu, but I'm not sure when. I'll defer to @hernandito if it's something he wants to take a shot at. Thanks! Latest version does need Folder.View 2023.09.22-1 for the autostart styles to work. https://github.com/Tyree/folder.view.custom.css

Significant update to the dashboard and docker page css. Per @Masterwishx request to be able to pick other icons other than basic play/stop, I've baked in the ability for users to easily change the started and stopped icons via custom properties at the top of the file. Instructions are in the file. https://github.com/Tyree/folder.view.custom.css If you're using an older browser that doesn't support custom properties in CSS, you'll have to find and replace the variables within the style declarations and replace them with the values of those variables. Here is an excerpt of the file showing the custom properties: /* EXPANDED FOLDER HEADER AND "DRAWER" */ --exfold-header-bg-c: rgba(255, 255, 255, 0.1); --exfold-drawer-border-c: rgba(255, 255, 255, 0.1); /* ICONS */ --folder-started-icon: "\f04b"; /* Normal started icon - default is play triangle */ --folder-stopped-icon: "\f04d"; /* Normal stopped icon - default is rounded square */ --folder-autostart-full-icon: "\f144"; /* Indicate ALL autostart containers within the folder are started */ --folder-autostart-partial-icon: "\f144"; /* Indicates SOME autostart containers within the folder are started */ --folder-autostart-off-icon: "\f144"; /* Indicates NO autostart containers within the folder are started */ --container-started-icon: "\f04b"; /* Normal started icon - default is play triangle */ --container-stopped-icon: "\f04d"; /* Normal stopped icon - default is rounded square */ --container-autostart-started-icon: "\f144"; /* Indicates autostart container is started */ --container-autostart-stopped-icon: "\f28d"; /* Indicates autostart container is stopped */ --container-spin-icon: "\f110"; /* Spin icon temporarily shown between container stopping and starting */ /* ICON COLORS */ --folder-started-icon-c: #4caf50; /* Normal started icon - default is green */ --folder-stopped-icon-c: #f0000c; /* Normal stopped icon - default is red */ --folder-autostart-full-icon-c: #4caf50; /* Indicate ALL autostart containers within the folder are started */ --folder-autostart-partial-icon-c: #e68a00; /* Indicates SOME autostart containers within the folder are started */ --folder-autostart-off-icon-c: #f0000c; /* Indicates NO autostart containers within the folder are started */ --container-spin-icon-c: #e68a00; /* Spin icon temporarily shown between container stopping and starting */ --container-started-icon-c: #4caf50; /* Normal started icon - default is play triangle */ --container-stopped-icon-c: #f0000c; /* Normal stopped icon - default is rounded square */ --container-autostart-started-icon-c: #4caf50; /* Indicates autostart container is started */ --container-autostart-stopped-icon-c: #f0000c; /* Indicates autostart container is stopped */ /* ICON SIZES */ --folder-status-size: 16px; --exfold-status-size: 20px; --container-status-size: 16px;

When I first started editing the custom CSS files, I was unable to get the import/export to work. I would make changes to my file on my desktop, try to import and nothing would change. When I checked the CSS file in the plugins folder, it was still blank. Nothing had been imported. So I started working directly with the files in the plugins folder. I haven't tried it again since, but I can give it another go and see what it does. @hernandito has the same thing in his README. Not sure if he had the same issues or not.

Oh nice! This will be fun to dig into! Thanks! CSS files on my repo have been updated to include minimum folder.view version. Also added to README. Will update again once I implement styles for the new autostart classes. https://github.com/Tyree/folder.view.custom.css Thanks!

I'm trying to remove a binhex-nzbget container and it keeps coming back after a few minutes. I delete it the typical way, click and then choose remove. I choose the option to also delete the image. I even go in a delete its config folder from appdata. A few minutes later, it's not only back but supposedly even started. I have disabled and reenabled docker. I've even rebooted the server. It refuses to go away. What else can I try?

Glad you're starting to see some light at the end of that tunnel, bud! I didn't start with one of yours, I was living under a rock and didn't realize you had that repo until @Masterwishx had a conflict between our code today. 😄 I knew about your icon gallery, but not the custom CSS. I followed your lead and posted my files on GitHub. You can feel free to just fix it how you think best and incorporate into your package if you like. I'm sure what I have can be cleaned up even more than I have done, but it works. 😄 https://github.com/Tyree/folder.view.custom.css I tried to use specificity over !important, but I'm interested to see how you would improve things.

So, thanks to @Masterwishxpointing out an issue, I realized I had way too much extraneous code. I was trying to add a new icon when I decided to just replace the existing icons, but I left all the extra code still in there. Anyway, here's the new code for the dashboard and docker page autostart icons (Full code can be found here: https://github.com/Tyree/folder.view.custom.css ): /*************************************************/ /* AUTOSTART ICONS - DASH */ /*************************************************/ #docker_view .outer:not(.folder-docker).autostart.started i:not(.fa-spin)::before { content: "\f144"; /* Replace the green triangle with a different icon */ } #docker_view .outer:not(.folder-docker).autostart.stopped i:not(.fa-spin)::before { content: "\f28d"; /* Replace the red square with a different icon */ } #docker_view .outer:not(.folder-docker).autostart.started i.fa-spin::before, #docker_view .outer:not(.folder-docker).autostart.stopped i.fa-spin::before { content: "\f110"; /* Replace the spinner with a different icon */ } /*************************************************/ /* AUTOSTART ICONS - DOCKER PAGE */ /*************************************************/ .outer:not(.folder-outer).autostart i.started:not(.fa-spin)::before { content: "\f144"; /* Replace the green triangle with a different icon */ } .outer:not(.folder-outer).autostart i.stopped:not(.fa-spin)::before { content: "\f28d"; /* Replace the red square with a different icon */ } .outer:not(.folder-outer).autostart i.started.fa-spin::before, .outer:not(.folder-outer).autostart i.stopped.fa-spin::before { content: "\f110"; /* Replace the spinner with a different icon */ }

Absolutely. All these little tweaks are just sprinkles on the icing on the cake. 🙂

Yeah, those will have to be conditions that @scolcipitato would have to code in classes for, so we can select them for styling. Someone smarter than me might be able to figure out some clever way to accomplish this with CSS alone, but it'd be WAY smoother with the classes in place. 🙂

What you're asking for may be impossible with CSS alone since there's nothing on the folder element itself to flag the condition you speak of. Was the orange stop button based on only autostart containers or if ANY containers in the folder were stopped?

Ah okay. Weird. I assume it's supposed to be class="appname" like other places.

Ah! Yes indeed! Yep. Couldn't do any of this new CSS without that update. 🙂

This does the same thing as my last post, but for the docker page instead of the dashboard: /*************************************************/ /* AUTOSTART ICONS */ /*************************************************/ .outer:not(.folder-outer).autostart .inner i:not(.fa-spin)::before { display: inline-block; font: normal normal normal 14px/1 FontAwesome; margin-right: 4px; } .outer:not(.folder-outer).autostart .inner i.started:not(.fa-spin)::before { content: "\f144"; color: #4caf50; } .outer:not(.folder-outer).autostart .inner i.stopped:not(.fa-spin)::before { content: "\f28d"; color: #f0000c; } .outer:not(.folder-outer).autostart .inner i.started.fa-spin::before, .outer:not(.folder-outer).autostart .inner i.stopped.fa-spin::before { content: "\f110"; }

I went kinda simple here. I change the started/stopped triangle and square to use a circle version from font-awesome when set to autostart. Here's the code for it: /*************************************************/ /* AUTOSTART ICONS */ /*************************************************/ #docker_view .outer:not(.folder-docker).autostart .inner i:not(.fa-spin)::before { display: inline-block; font: normal normal normal 14px/1 FontAwesome; margin-right: 4px; } #docker_view .outer:not(.folder-docker).autostart.started .inner i:not(.fa-spin)::before { content: "\f144"; color: #4caf50; } #docker_view .outer:not(.folder-docker).autostart.stopped .inner i:not(.fa-spin)::before { content: "\f28d"; color: #f0000c; } #docker_view .outer:not(.folder-docker).autostart.started .inner i.fa-spin::before, #docker_view .outer:not(.folder-docker).autostart.stopped .inner i.fa-spin::before { content: "\f110"; }

@scolcipitato As I was inspecting the code for the classes you added, I noticed there's a class property on the span wrapping the container name text on the dashboard, but it has no equals or value: <span class>container name</span> Doesn't seem to be causing any problems, just pointing it out.

You da man. Thanks! I'll see what I can do with it. 🙂