luckyframework/lucky_cli

Including:

Cookie/Session accessing with .get and .get?
Cookie/Session setting with .set
Cookie removal with .expire
Session key removal with .unset
Flash.danger -> failure
Updating the FlashHandler
Updating the habitat settings for a new Lucky app including
Lucky::SessionCookie.key and Lucky::CookieJar.default_expiration
Removing old habitat settings (Lucky::Session::Store)

luckyframework/authentic#19

Previously, the test was asserting that a user that has signed in via
the backdoor auth flow was signed *out*.

Closes #232

Closes #242

Closes #243

Closes #215

* The Problem

External contributions that run on Travis CI don't have access to the
encrypted ENV vars. So when the Heroku deploy specs ran they failed
because the HEROKU_API_KEY and HEROKU_EMAIL were not set.

* The solution

Run Heroku specs based on the HEROKU_RUN_SPECS env variable. Then in
Travis set an encrypted HEROKU_RUN_SPECS variable. That way it is not
set for external contributions and the Heroku specs are skipped. This
should work fine since generally the Heroku specs work. They will run
whenever a new version is created since that will always be down by
someone with repo write/read access.

Closes luckyframework/lucky#521

Closes #214

…224

Closes #217

This is used by the Heroku buildpack

Note: in mosop/teeplate the changes for 0.24 hasn't been merged