phpFlickrSynch is a PHP application that reads the metadata of your photos stored on Flickr, stores them in a local MySQL database, and gives you an API to let you play with those metadata.
Why using phpFlickrSynch rather than the Flickr API?
- Because you appreciate to have a copy of all your Flickr data in a local database (think data portability),
- Because you want to do complex mashups between Flickr data and data you host (and you feel dealing with Flickr XML API makes things too complex).
- Because you feel performance is better when accessing local data rather than a web service.
Important: phpFlickrSynch doesn’t retrieve photos hosted on Flickr to store them on your local file system; it only deals with metadata.
- A local database that will store all the metadata of your photos,
- A read-access API to the local database,
- A backoffice that lets you synchronize your photo albums and belonging photos between Flickr and the local database,
- The great phpFlickr API that is used to communicate with Flickr API.
- PHP 5.x (with PDO database access extension)
- MySQL 5.x
How to install it?
- Unzip the phpFlickrSynch package in a directory that can be read by your web server;
- Create a database that will host the phpFlickrSynch tables;
- Execute the SQL file named “/phpFlickrSynch/setup/create.sql” to create the phpFlickrSynch tables in your database;
- Follow the phpFlickr authentication page to create your Flickr API Key, Secret and Token;
- Register a Yahoo! GeoPlanet Application ID at the Yahoo! Developer Network site
- Copy the “/phpFlickrSynch/phpFlickrSynch_config_sample.php” to “/phpFlickrSynch/phpFlickrSynch_config.php” and fill in the values (database connection, Flickr key, Yahoo App ID)
- Access the backoffice at “/phpFlickrSynch/backoffice/” (it is recommended to protect access to the backoffice i.e: using .htaccess security); and get a quick introduction to this tool
- Include the “/phpFlickrSynch/phpFlickrSynch.php” in any PHP file that will use the phpFlickrSynch API; and learn more how to use the API
- Mar, 3rd 2010 – Initial release