In old versions of unRAID (I'm thinking 4 and early 5?), the mover would ignore folders that had a leading period (e.g., ".apps").  Another nice perk is it doesn't show up when browsing my SMB shares on a Mac.

 

I currently have my docker.img file and appdata folder in the root of my cache.  But since I have no reason to access either of those items via SMB, I'd rather not have them even show up.  So I've been tossing around the idea of creating a ".docker" folder for the image and changing my appdata folder to ".appdata" ...

 

Now, the only reason I'm hesitating is that I recall some plugins (earliest version of Plex, for example) didn't do too well with living in a folder with a leading period.  Pretty sure it became recommended practice to avoid folders with trailing periods for plugins.  Anyone have some recent experience with this scenario?

 

Thanks!

You can make a share called appdata on your cache drive and set it to “Cache only”, that way the mover leaves it where it is. Same goes for all folders you make under that share. You can change the SMB settings for appdata share if you like “hide it” from your Mac.

I do as Leifgg, plus when you're getting everything set up it's quite useful to have access to appdata for configuring things.  I'm not a Mac user so can't offer any insight into that side of things.

Thanks all.  My apologies if I didn't explain my situation well, but I already utilize a cache-only share called "appdata".  I guess I just don't want to see it (or the docker.img) commingling with the other shares on the cache drive.  I'm weird I guess.

Then easiest thing is to change the smb setting and make the share invisible.

Export: Yes (hidden)

Security: Private

 

You won't see it when browsing, but anyone with private access can still get to it by specifying the path.

Man, I'm really doing a terrible job explaining what I mean.  All my user and disk shares are exported as hidden.  I more mean when I connect to my cache share via SMB, I see the "appdata" folder and disk.img among all the folders that will ultimately be cleared from the cache when the mover kicks in.  But often times I access the cache directly to prevent my drives from spinning up (and I only have the mover run once per week).

 

My thought was to change the appdata folder to ".appdata" and put the docker.img file into a ".docker" folder so they would essentially be hidden when browsing the cache share.

 

In the end I think I'll abandon this thought as it seems to be a pretty unique use case and I shouldn't worry that much about preventing disk spinups.  So I'll just change me

Or maybe I'm not all that crazy for wanting to do this!  Here's a post about someone accidentally deleting their docker.img when doing some house cleaning.

 

http://lime-technology.com/forum/index.php?topic=39083.0

 

OK, now I see what you mean.  Why don't you just try it and see?

Yeah, I will.  Was just wondering if anyone had tried it, successfully or unsuccessfully, before I went down that road.

I run all my folders on my cache drive in .directory's.

Before unRAID implemented the Cache only share it was the easiest way to not have them moved.

The Moves still does not move any folders with a leading period.

 

I currently have:

.docker\docker.img

.Programs\all my 'appdata' program folders in here

.Torrents\for all my torrent downloads and seeding.

Just to spell it out in more detail.

 

Mover will not move any hidden folders (those with a leading .) in the ROOT of cache, or any folders in the ROOT of cache with the share set to cache-only, or any files in the ROOT of cache.