Totally OT - I need some heads up (and a hug or two)
J. Landman Gay
jacque at hyperactivesw.com
Thu Oct 9 14:39:46 EDT 2008
Malte Brill wrote:
> Hi all,
>
> today is the worst day in my self employment life. I arrived at the
> office today, just to learn that everything apple branded is gone.
> Stolen. Away.
Malte, I'm so sorry. I know exactly how you must feel. Your heart just
sinks, it is horrible. I think all of us can empathize, this is our
worst nightmare. Big, big hug.
For what it is worth, I've posted a tiny little utility that I use all
the time. It isn't polished or beautiful, it's just a simple little tool
that I have been using for years. I suspect most of us have something
like this, but for anyone who wants to grab a copy, it's here:
<http://www.hyperactivesw.com/downloads/ftp_upload.rev.zip>
This is a very basic little stack that just uploads the current topstack
to my FTP backup directory. It also contains a button that lets you
choose any other file on disk instead for upload. Before uploading, it
gzips the file, adds a date stamp to the name, and then sends it.
You will need to change the first line of the card script to point to
the location of your online ftp backup directory. Since the script does
include your ftp password in the URL, I password-protect my copy of the
stack to prevent anyone seeing the full URL. It wouldn't be hard to
change the utility to ask for the password on each access; I've always
been too lazy to type it in each time so I leave it stored in the script.
I have a backscript with a handler like this:
on bup
go stack "path/to/FTP_Upload.rev"
end bup
When I am working on a stack, I just type "bup" into the message box
periodically and this little utility appears with my current stack
already loaded into the "file to back up" field. I just hit the "upload"
button and away it goes. Each upload is gzipped and date-stamped on the
server. It currently does not include the time in the stamp, so each
upload on the same day overwrites the previous one. That's all I need
generally but you could change the script. I keep other copies locally,
but this way the most current version is always on the remote server.
Anyone who wants this, go ahead. It isn't pretty or sophisticated, and
I'm sure others have fancier utilites than this one, but it's a start
for anyone who wants it.
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode
mailing list