mounting masq
Masq migrations

The result of running `rake masq:install:migrations`
And the database schema

The result of running `rake db:migrate`
Set development settings for masq

Mostly, the host key is mandatory for activation emails. Without it, rails
errors.
Beginnings of a monkey patch

To get browserid-provider to use Masq's credentials. All it needs is the
currently logged in user's email address.
Better explanation for protect_phishing per dennisreimann/masq#9
Syntax highlight the other two shell snippets
In development, don't send emails

More pain than they're worth in development, and I've confirmed it works
otherwise.
Disable email_as_login in masq as it's currently broken

See dennisreimann/masq#3 for more details.
A heroku specific environment config file
Configure browserid-provider

Also had the old URL. Oops. :blush:
Fix the syntax error

double oops :blush: :blush:
Documentation mismatch: login_path

BrowserID::Provider's documentation says 'authentication_path', however it
actually uses 'login_path' internally
Monkeypatch BrowserID::Provider

One is to integrate BrowserID::Provider with Masq's user session data. The other
is to fix a bug until >0.5.6 comes out. (The configuration parameters are reset
without the hotfix to initialize.)