Currently we ssl to 'disable'. That doesn't work with databases hosted by www.databaselabs.io as they (quite reasonably) require ssl.
We need to handle this better.
We will no longer set ssl mode in the front-end. Instead in the backend we'll default to 'require'. If that fails we'll try 'disable' and finally 'verify-full` (although I don't think it can ever work as it seems to require local certificate http://www.postgresql.org/docs/9.0/static/libpq-ssl.html).
Currently we ssl to 'disable'. That doesn't work with databases hosted by www.databaselabs.io as they (quite reasonably) require ssl.
We need to handle this better.
We will no longer set ssl mode in the front-end. Instead in the backend we'll default to 'require'. If that fails we'll try 'disable' and finally 'verify-full` (although I don't think it can ever work as it seems to require local certificate http://www.postgresql.org/docs/9.0/static/libpq-ssl.html).
Only if all fail we'll report an error.