shattered

Has anyone else using Windmill been able to configure a resource to read/write files in user shares? I'd like for a script I run in Windmill to be able to save files locally but I don't see any explanation of how to do this in the docs. They seem to emphasize storing files in the cloud but that's just not practical for my use. I'm sure there's a way to do it by exposing a path in the container config and then adding a resource with the path but I can't figure out. Any help would be greatly appreciated! And I'd love to hear what you use Windmill for too! FYI, there is no Windmill support forum so that's why I posted here.

I'm trying to figure out the simplest way to backup everything (5 total shares, 3 cache only) to a single HDD which I can periodically connect to the server but otherwise keep disconnected/offsite. I currently only backup to gsuite using rclone but I'd like to have an HDD with everything that I could drop in a new server in a worst case scenario. Is there a docker or script that would simplify this? Something that would sync every share to the single drive, my server is about 8 TB.

I figured it out! It is possible to migrate from Windows 10 to a docker container but it takes a couple steps, I'll try to explain what I did. 1. BEFORE shutting down your Windows setup, back-up the Stash data files (should be folders .stash, cache, generated, metadata) the most important of these is the stash-go.sqlite file within .stash, the config is less important because you have create a new config for the docker to identify the new file paths 2. Install the Stash docker container. I kept the default folder locations within the appdata share so I knew where to move stuff, the data path should be something like /mnt/user/share/file/path/ 3. Make Stash scan the new library, all of your 'media' should appear but without your precious metadata 4. Stop the Stash docker container 5. Delete *most* of the generated folders in the appdata folder and copy your original data over. You must keep the config file and folder names that the docker generated or it won't work. On Windows the config file was stored in the .stash folder but in the docker it's in a folder named config 6. Start the Stash docker container, now your metadata should be attached to all the right files (performers are attached to scenes, studios attached to scenes, etc.), BUT the files will be unplayable because it's trying to find the file where it was on Windows 7. Make Stash scan the library again and it should update the file locations while keeping your metadata in place I hope this helps the next guy upgrading their system! Also, I didn't try this out but it might work, in Settings > Tasks there's an option to export and import JSON data, this might do the trick

Has anyone had any luck moving a Stash setup from Win 10 to a docker? I copied all of the Stash data from my Windows storage to unRAID but I'm having trouble mapping the folders (config, metadata, cache, generated) to the docker. Stash is able to find the data files but can't seem to find/apply the previous database info (studios, performers, scene data, etc.). I suspect the problem is either I have the wrong file paths or the SQLITE file will need to be edited to reflect the new data file locations... But I'm a total noob with this stuff so any help is greatly appreciated!