Make Facebook login work again: tweak db column length.
Stop using Play Evolutions

Remove all database evolution scripts. There's some non backwards
compatible change in Play 2.2.x, which results in Play trying to apply
all down evolutions (!). Also see:
  https://groups.google.com/d/msg/play-framework/8HoNAE5KTxo/RHdU9aZZoHgJ
  """While migrating from 2.1.x to 2.2.x  play wants to run evolutions on
  the database for no reason. Essentially recreate the entire schema (data
  loss).
  [...]
  In my case that was due to two things.
  [... different] prefix whitespace [...]"""
  + different order when checking evolutions.

Stop using Play Evolutions, non-backw-compat changes feels crazy. Instead
I'll use Flyway http://flywaydb.org/, which is more flexible and also
supports Java/Scala evolutions.
Make `dependency-graph` work.
Start using Flyway 3.0

And remove old no longer needed migration Evolution001.
Add db migration v2014_06_26__base_version.sql

It recreates the current schema version. I generated it like so:
$ pg_dump --host 127.0.0.1 -p 55432 --username=debiki_prod \
  --schema-only --no-tablespaces --use-set-session-authorization \
  > src/main/resources/db/migration/2014/v2014_06_26__base_version.sql
where 55432 is a tunnel to the production env host.
Remove bad commands from base schema version script.
Apply evolutions before starting search engine

The search engine accesses the database.
Create SCHEMA_VERSION automatically, rename Flyway .sql to v1, v2 etc.