adjusting comments

This commit is contained in:
Taylor Otwell 2015-12-03 22:26:09 -06:00
parent ff35b10a3d
commit 3fa12671ce
1 changed files with 8 additions and 4 deletions

View File

@ -55,6 +55,10 @@
| users are actually retrieved out of your database or other storage | users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data. | mechanisms used by this application to persist your user's data.
| |
| If you have multiple user tables or models you may configure multiple
| sources which represent each model / table. These sources may then
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent" | Supported: "database", "eloquent"
| |
*/ */
@ -65,7 +69,7 @@
'model' => App\User::class, 'model' => App\User::class,
], ],
// 'database' => [ // 'users' => [
// 'driver' => 'database', // 'driver' => 'database',
// 'table' => 'users', // 'table' => 'users',
// ], // ],
@ -80,9 +84,9 @@
| that is your password reset e-mail. You may also set the name of the | that is your password reset e-mail. You may also set the name of the
| table that maintains all of the reset tokens for your application. | table that maintains all of the reset tokens for your application.
| |
| Of course, you may define multiple password resetters each with a their | You may specify multiple password reset configurations if you have more
| own storage settings and user providers. However, for most apps this | than one user table or model in the application and you want to have
| simple configuration with Eloquent is just perfect out of the box. | seperate password reset settings based on the specific user types.
| |
| The expire time is the number of minutes that the reset token should be | The expire time is the number of minutes that the reset token should be
| considered valid. This security feature keeps tokens short-lived so | considered valid. This security feature keeps tokens short-lived so