Trippy idea.

Hi Ferrix,

attached a diff for the --mayi idea. The knowledgeable program must return an error code of 0 if it wants the file to be uploaded to s3. Anything else and the file will not be uploaded. I chose this way as if the knowledgeable program is missing or produces any other kind of error the file will still be backed up.

the syntax of mayi changed a bit since my first request in that it takes '%s' instead of '%1' as this was easier with me not really knowing ruby.

I now have:
s3sync.rb -s -r --delete --mayi="isstarred.py %s" <dir> <bucket>
in my upload scripts. the python script only returns 0 for images with a IPTC rating of 1 and above which does wonders for the amount of data I need to upload :-)

regards
  charlie

Hi Ferrix,

first as always, great util !!

I have used it to backup about 15k photos and the collection is continually growing (1400 photos/4,7GB for the last outing). What I am now starting to dearly miss is a way to tell S3Sync not to backup certain photos (not 100% in focus; wrong person in frame and all that kind of thing; I still have them on the local hd, but if my flat burns down losing them would be the least of my problems).

THUS: --mayi "mayiuploadfile %1"
which would call the external program 'mayiuploadfile %1' with the path+filename of the file about to be uploaded as it's parameter and depending on it's exit code S3Sync will upload the file to S3 or skip it. Thus 'mayiuploadfile' could be a shell script or an assembler program that knows what file it expects and processes it accordingly (creating this program is left as an exercise to the reader).

This feature would let me tag the photos that i want uploaded to S3; someone else might use it to only upload files newer than a certain date ("mayiuploadfile -newer 20070101 %1") or only upload mp3's with at least a bitrate of 128kb/s ("mayiuploadfile -eqgt 128 %1") or whatever else they feel like.

Thanks for your consideration of this feature and regards
  charlie

I don't understand why don't you juse use -s instead of changing the code?

maybe I titled my post/request badly

I felt that when I defined SSL_CERT_DIR I was already telling s3* to use SSL and that the -s is thus redundant. I would prefer that once I set SSL_CERT_DIR all my s3 requests default to secure without further intervention.

regards
  charlie

Hi

Would it be possible to make a --no-ssl option

currently when a new version of s3sync arrives I change line 37 s3try.rb from
                if $S3syncOptions['--ssl'] and $SSL_CERT_DIR
to
                if $SSL_CERT_DIR or $S3syncOptions['--ssl']

so that if I have $SSL_CERT_DIR defined s3cmd and s3sync default to ssl connections. Thus a
                if $SSL_CERT_DIR and not $S3syncOptions['--no-ssl']
would be a (for me) nice feature if things default to secure.

regards
  charlie