Delete unused photos_helper.
Don't recreate photos, but update metadata.
Display all photos on index page.
Plantings HABTM photos.
Connect plantings to photos.
show photos on planting page
show plantings on photo page
photo and planting owners must match
added alt tag
Merge pull request #210 from Skud/photos

Photos
changed flickr_photo_id to string

... because integer worked fine in dev (on sqlite3) but broke on staging
(with postgres). Turns out flickr photo IDs are quite LARGE integers.
But really they could be anything, so string seems safest.
Merge pull request #211 from Skud/photos-fix

changed flickr_photo_id to string
rearranged notes/pics on plantings page
Avoid duplicate photos on plantings (or vice versa)

Strictly speaking this doesn't prevent you adding them if you really
try, but the validation for that was beyond what I could figure out (the
docs don't help, and all SO/blog posts are outdated and didn't
work).

However, if you do somehow manage to add dups, you will never see them
again thanks to the :uniq => true in the model.  That's good enough for
me.
Merge pull request #212 from Skud/photos-view-tweak

Photos view tweak
Reverted uniqueness limits for photo/planting association

It seems this interacts badly with the default_scope on postgres (but
    not on sqlite3).  Error message from the logs:

2013-06-01T02:21:05.312099+00:00 app[web.1]: ActiveRecord::StatementInvalid (PG::Error: ERROR:  for SELECT DISTINCT, ORDER BY expressions must appear in select list
2013-06-01T02:21:05.312099+00:00 app[web.1]: LINE 1: ...photo_id" = 2 AND "plantings"."id" = 181 ORDER BY created_at...
2013-06-01T02:21:05.312099+00:00 app[web.1]:   app/controllers/photos_controller.rb:59:in `create'
2013-06-01T02:21:05.312099+00:00 app[web.1]:                                                              ^
2013-06-01T02:21:05.312099+00:00 app[web.1]: : SELECT  DISTINCT 1 AS one FROM "plantings" INNER JOIN "photos_plantings" ON "plantings"."id" = "photos_plantings"."planting_id" WHERE "photos_plantings"."photo_id" = 2 AND "plantings"."id" = 181 ORDER BY created_at desc LIMIT 1):

For now, we'll just have to rely on the controller (which adds the
association) to keep things unique.
Merge pull request #213 from Skud/fix-photos-again

Reverted uniqueness limits for photo/planting association
added deploy tasks script
Merge pull request #214 from Skud/deploy-tasks

added deploy tasks script
Merge pull request #215 from Growstuff/dev

Production push: photos, crop wrangling, rss