iRev How do I manage a different folder full of images
jimaultwins at yahoo.com
Tue Dec 22 01:01:12 EST 2009
See Sarah's reply that discusses the most logical way to do the irev-
script-call (cron job from cPanel).
Actually, any way you can start the irev script that would look at the
various folders on the various servers and hard drives would cause the
When I was running a server at a real estate company about 10 years
ago, I had an Applescript send me an email every five minutes so that
I could tell if it was running, and if not, when it had stopped. This
would be overkill for you, but an email a day could do the trick.
All you would have to do is call the irev script from any computer.
You could make a small app and have it do:
on updateTrigger --running on your computer
if button "ckbxRunning" is true then
get url ("http://myaccount.on-rev.com/task/updateCatalog.irev")
--this merely triggers the script to do its thing
send "updateTrigger" to me in (60*60*12) seconds
Also, you could trigger the script from any browser or server that
runs a script or displays a page using html.
On Dec 21, 2009, at 4:08 PM, Thomas McGrath III wrote:
> Jim, Is this a cPanel thing? When I get home I will look into that
> if so...
> On Dec 21, 2009, at 6:57 PM, Jim Ault wrote:
>> Why not build and maintain a catalog of the folders on On-Rev, then
>> let it decide what needs to move or go away.
>> On Dec 21, 2009, at 3:03 PM, Thomas McGrath III wrote:
>>> The exact numbers are not important yet because I don't know how
>>> many will be uploaded (could be thousands).
>>> So, the best way I know how to describe what I am doing is that
>>> the Main folder is used for a pre determined number of images to
>>> be viewed on the Main website as "Latest uploads". But I want to
>>> mirror them in another folder that can't handle more than 100 at a
>>> time since that folder is viewed from a special Mobile site via
>>> Pipho/Jaipho that can't handle downloading more than 100 at a time
>>> without a major slow down of download time. BUT I could move new
>>> images into the Remote folder IF I move the oldest into another
>>> folder until that folder fills up and then I need to do it again
>>> when that fills up. etc.
>>> I don't need them to move per image and was thinking that I can
>>> move them based on a chunk of time (week or month) instead - as
>>> long as the Remote folders don't have too much more than 100 at a
>>> time. I could name the remote folders based on dates etc. This
>>> seems best as only the first remote folder would need watched and
>>> when it reaches 100 then maybe then I could just dump them all
>>> into another folder.
More information about the Use-livecode