jcofer555

sounds good, i'll have an update out soonish

exclusions are just to exclude from moving, i have it set currently to delete empty folders/datasets after moving but i could make it a checkbox option if you'd like

avoidance of linking config files and breaking one or both and performance so it doesn't have to scan the metadata of every file and instead only those extensions with those being the most common. i used the example from trash guides for the command

nice, glad to hear it's better if [[ "$ENABLE_JDUPES" == "yes" ]]; then if command -v jdupes >/dev/null 2>&1; then TEMP_LIST="/tmp/automover_jdupes_list.txt" HASH_DIR="$HASH_PATH" HASH_DB="${HASH_DIR}/jdupes_hash_database.db" # Ensure HASH_DIR if [[ ! -d "$HASH_DIR" ]]; then mkdir -p "$HASH_DIR" chmod 777 "$HASH_DIR" else echo "Using existing jdupes database: $HASH_DB" >> "$LAST_RUN_FILE" fi if [[ ! -f "$HASH_DB" ]]; then touch "$HASH_DB" chmod 666 "$HASH_DB" echo "Creating jdupes hash database at $HASH_DIR" >> "$LAST_RUN_FILE" fi # Extract destination file paths from Automover log grep -E -- ' -> ' "$AUTOMOVER_LOG" | awk -F'->' '{gsub(/^[ \t]+|[ \t]+$/, "", $2); print $2}' > "$TEMP_LIST" if [[ ! -s "$TEMP_LIST" ]]; then echo "No moved files found, skipping jdupes step" >> "$LAST_RUN_FILE" return fi # Determine affected shares from destination paths (e.g., /mnt/user0/movies) mapfile -t SHARES < <(awk -F'/' '$2=="mnt" && $3=="user0" && $4!="" {print $4}' "$TEMP_LIST" | sort -u) # Excluded shares EXCLUDES=("appdata" "system" "domains" "isos") for share in "${SHARES[@]}"; do # Skip excluded shares skip=false for ex in "${EXCLUDES[@]}"; do [[ "$share" == "$ex" ]] && skip=true && break done [[ "$skip" == true ]] && { echo "Skipping excluded share: $share" >> "$LAST_RUN_FILE" continue } SHARE_PATH="/mnt/user/${share}" [[ -d "$SHARE_PATH" ]] || { echo "Skipping missing path: $SHARE_PATH" >> "$LAST_RUN_FILE" continue } echo "Jdupes processing share $share" >> "$LAST_RUN_FILE" # Run jdupes on this share’s destination folder /usr/bin/jdupes -rLX onlyext:mp4,mkv,avi -y "$HASH_DB" "$SHARE_PATH" 2>&1 \ | grep -v -E \ -e "^Creating a new hash database " \ -e "^[[:space:]]*AT YOUR OWN RISK\. Report hashdb issues to jody@jodybruchon\.com" \ -e "^[[:space:]]*yet and basic .*" \ -e "^[[:space:]]*but there are LOTS OF QUIRKS.*" \ -e "^WARNING: THE HASH DATABASE FEATURE IS UNDER HEAVY DEVELOPMENT!.*" \ >> "$LAST_RUN_FILE" echo "Completed jdupes step for $share" >> "$LAST_RUN_FILE" done else echo "Jdupes not installed, skipping jdupes step" >> "$LAST_RUN_FILE" fi fi

i released a new update with some more css changes, hopefully it helps

yes i suspected some of them would still be off, glad to hear the vertical is good. will work on the others over time but can't guarantee anything

2025.10.81.4 update hopefully helps with the smaller screens

yea not sure how much better css will get to be honest, i'm not very good with it and dealing with multiple size screens is not an easy thing. likely the smaller the screen the more issues people will notice sadly. i'll do what i can but have 0 devices to test with so it's not super likely i'll be able to fix all of them. stacking them would just pose a similar issue as they grow in height one would get pushed out on smaller screens when one gets long that or i'd have to set max heights which has it's own nuances

good catch, that section was meant to be deleted, it's a duplicate to what is at the top. on the next update it'll be removed

What browser? I just tested with os 7.1.4 with both Firefox and edge on windows and they were fine

What os version are you on?

unraid doesn't have a "disable" option for the mover yet, hopefully they are going to include the option at some point. best you do can is set it for monthly and then the rest of the month the plugin will do the job. once unraid offers a disabled option then you can just use that and yea this plugin would monitor and move the files based on your share settings and the filters used

the removal of unraid mover has been removed from this plugin due to the complexities of how it needs to be implemented

just added age based moving as well, working on more stuff too

that's how the new version i put out the other day does it actually :) so if you are on the newest version then that's how it'll work for ya

this uses the built in mover so when it "moves" it moves all shares based on the shares settings just like if you used the regular mover, what this plugin does is offers the ability to prevent the mover from running unless the selected pool meets the threshold and then offers logging for which files were moved on or off the selected pool. i don't think there is a way i can offer to pick which shares to move with how the plugin uses the built in mover it would have to be a customized mover using rsync like mover tuner uses to do that which i don't plan to dive into

added some safety checks for modifying the schedule to hopefully prevent future 0kb mover binaries

it should fix it if you reboot, if it doesn't let me know

what version of automover?

you don't have the share setup correctly to use mover, you need to have primary storage set as cache, secondary storage set as array and mover direction cache -> array. mover tuning being uninstalled will reverse whatever was tuned, best to reboot unraid after removing it though

ah yea must have been hidden, i see it now and agree likely share not configured correctly.

yea it's what got me started with this plugin actually. my wants are threshold, it's own scheduler, logging, move by age, and exclusion list. not sure if i'll get age or exclusion or not but gonna try

disabling is essentially already allowed by just putting 0 for the threshold %, age related i looked into at one point and struggled with it but i might give it another go at some point as it would be an addition i'd like as well

curious on what this comment is in reference too as apart of my plugin? i don't see foamy having written messages here