Fix for new installations to prevent Integrity constraint violations

New feature lets users reference requests to api_key_id in the api_logs table but requests not logged will throw an SQLException SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails because api_key_id is not set to nullable.

Fix is simply making it nullable as described in #48

Backport logging feature of v2.1+

Backport features from v2.x

Specifically, commits 529424eb5a3e06c4d884d49e5ffd1fb65d60fa67, 586297331d95c6ed9a1f011ea3f9d919b695de38

Access the ApiLog instance from the controller

Useful if we want to reference an API call to a transaction.

Hotfix for api-key generation

As described by @jotafurtado in #42.

Logging at method level

You can set logging at method level by using the logged option. By default for all methods in api-guard, the option logged is set to true. Set it to false to exclude that method for logging.

Laravel 5.0 Public Release

Hurrah!

Laravel 4.2.x Public Release

Note that upgrading to this release from old ones will require you to change the namespaces of some classes.

• Chrisbjr\ApiGuard\ApiGuardController to Chrisbjr\ApiGuard\Controllers\ApiGuardController
• Chrisbjr\ApiGuard\ApiKey to Chrisbjr\ApiGuard\Models\ApiKey