Use GoogleCL to Upload Photos to Picasa Web Album
Productivity Sauce
If you are using Google's Picasa Web Album photo sharing service and you want to automate the process of uploading photos, the GoogleCL command-line toolset can come in rather handy. Once installed on your machine, you can use it to perform several tasks such as creating albums, uploading and tagging photos, downloading photos, etc. directly from the command-line. Better yet, GoogleCL is pretty straightforward in use. For example, you can upload all photos in a directory to a specific album using the following command:
google picasa post --title "Travel Photos" /home/user/photos/*.jpg
If the specified album doesn't exist, GoogleCL automatically creates it for you. When you run GoogleCL for the run, you have to authorize it for use with the Picasa Web Album service.
To automate the uploading process you can write a simple Bash script and create a cron job to run it on a regular basis. The script below uploads all photos in the /home/user/photos directory to the Travel Photos album and then empties the directory:
#!bin/bash google picasa post --title "Travel Photos" /home/user/photos/* echo "Photos have been uploaded." rm /home/user/photos/*.jpg
If you want to tag the photos during upload, then the command should look something like this:
google picasa post --title "Travel Photos" --tags berlin /home/user/photos/*
To run the script on a regular basis, you need to set up a cron job. Run the crontab -e command, specify the following cron job (replace the sample path with the actual path to the upload script) and save the modified crontab file:
@hourly /home/user/picasaupload.sh >> /home/user/picasaupload.log
This cron job will run the script every hour and log the result in the picasaupload.log file.
Comments
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Fedora Asahi Remix 41 Available for Apple Silicon
If you have an Apple Silicon Mac and you're hoping to install Fedora, you're in luck because the latest release supports the M1 and M2 chips.
-
Systemd Fixes Bug While Facing New Challenger in GNU Shepherd
The systemd developers have fixed a really nasty bug amid the release of the new GNU Shepherd init system.
-
AlmaLinux 10.0 Beta Released
The AlmaLinux OS Foundation has announced the availability of AlmaLinux 10.0 Beta ("Purple Lion") for all supported devices with significant changes.
-
Gnome 47.2 Now Available
Gnome 47.2 is now available for general use but don't expect much in the way of newness, as this is all about improvements and bug fixes.
-
Latest Cinnamon Desktop Releases with a Bold New Look
Just in time for the holidays, the developer of the Cinnamon desktop has shipped a new release to help spice up your eggnog with new features and a new look.
-
Armbian 24.11 Released with Expanded Hardware Support
If you've been waiting for Armbian to support OrangePi 5 Max and Radxa ROCK 5B+, the wait is over.
-
SUSE Renames Several Products for Better Name Recognition
SUSE has been a very powerful player in the European market, but it knows it must branch out to gain serious traction. Will a name change do the trick?
-
ESET Discovers New Linux Malware
WolfsBane is an all-in-one malware that has hit the Linux operating system and includes a dropper, a launcher, and a backdoor.
-
New Linux Kernel Patch Allows Forcing a CPU Mitigation
Even when CPU mitigations can consume precious CPU cycles, it might not be a bad idea to allow users to enable them, even if your machine isn't vulnerable.
-
Red Hat Enterprise Linux 9.5 Released
Notify your friends, loved ones, and colleagues that the latest version of RHEL is available with plenty of enhancements.
Synchronizing rather than uploading
I wrote a small jar to solve this problem. It is available here: http://vincesoft.blogspot.c...automatically-synchronize.html
No error checking
for example, when an error:
"Loading file /home/user/photos/1.jpg to album Travel Photos
Failed to upload /home/user/photos/1.jpg. (400: Bad Request)
1 photos failed to upload"