/tech/ - Technology★

sir we will take the job ,,, how much will u be paying and when do u need it by ,, our first couse of action will be to make a logo ,, .... and then we make a program in Java to do the backups

You have a Mac with Bash shell, but you're writing a Windows batch file. Is this correct? The simple solution would be something like this.

find . -type f -name "*.jpg" -exec mv {} newpath \;

>>1021575

shit that should be cp not mv

install open bsd

>>1021560 (OP)

You have a mac... whyy fuck around with bash scripting? use time machine.

>>1021600

/thread

>>1021560 (OP)

What you'd likely be willing to pay to someone who could do this competently would be insultingly low.

Look into rsync and figure out how to script it yourself.

Go back to Pooverflow, faggot.

>>1021567

lmao

>>1021575

>find . -type f -name "*.jpg" -exec mv {} newpath \;

find / -type f -name "*{.jpg,.JPG,.jpeg,.JPEG,.tiff,.TIFF,.raw,.RAW}" -exec cp -a {} newpath \;
"find /" to search from the drive root instead of current directory "find . "
{..jpeg...RAW..etc} to match other filetypes and lettercases
cp -a to archival copy while preserving attributes

Insert into a script and put an entry for the script into cron to execute periodically as needed.

>Mac

Gno

>>1021812

Extended globbing doesn't work in find, gnewfriend.

>>1021830

then use -iregex option instead

>>1021833

Or just grep -Ex, you know.

>>1021812

I wouldn't start find from root either. He's probably better off using rsync and keeping his images in the right folder.

man rsync

I recommend something like `find` to search and filter a list of items to `rsync`. Once you've got this working as you'd like, you can make an agent for `launchd` (the mac's reinvention of `crontab`) and run it on a schedule. This will be the most portable and extendable (e.g., it could be added into another script) solution.

Do NOT use TimeMachine or any GUI program to do this. You will end up with your data trapped in proprietary containers using proprietary file-formats, and the results will be less usable and probably slow to make any use of.

This is really a perfect way to introduce yourself to some shell-scripting and the command-line. It may take you two months to solve the problem on your own, but it'll save you years and thousands of dollars in the future when you've learned to do this kind of thing on your own, to solve all sorts of little problems like this, routinely.

Honestly, I'd recommend you still use the same resources/commands (at least `rsync` and `launchd` if needed) I've mentioned above, only I'd try to get familiar with Python and write a script using Python instead of Bash. If you don't end up writing many scripts in the future (unlikely), debugging an old bash script will be like reading hieroglyphics, whereas, a well written [and concise] Python script can be dang nigh close to English. The real advantage of using Python will be handling command-line arguments (if necessary), parsing strings and finding and filtering the files you want without esoteric shell commands whose options and arguments are going to be troubling to understand because their explanations will often be too formal. Personally, I find developing a script like this to be the most practical and efficient to do in Python; it's so easy to see the functions and methods and get some quick, offline help via the interpreter (using Python3 and tab-completion). Finally, you can also use Python on Windows (easier than bash). While I'd recommend a cursory familiarity with bash scripting because it'll basically be the language you speak to your computer when you've become accustomed to the CLI, writing scripts in Python has far greater utility and leverage.

You've already laid out your criteria, so it seems like you've given the problem some thought, and you're thinking about it in the appropriate manner, which is far beyond the average user's request for support. Just treat each of those criteria as a comment of pseudo-code and try to unravel how to translate each to actual code (Hint: The majority of this "unraveling" is basically going to be reading the manual pages for the listed programs and figuring out which options and arguments you need to pass in order to be able to filter out exactly what you need, or searching stackoverflow for "how to do x in python"). Your first script is going to be long and shitty, but that's okay. It's how you learn. What you will first write, which will do maybe 80-90% of what you need in 50 lines will one day be reduced to a thorough one-liner when you reach a greater level of competency, and you'll laugh and cry when you look back on the monstrosity that was your first script, but you'll smile on yourself for having taken that first step.