Gecko [ fastearnlimited.com ]

Name	Size	Permission	Date
app.php	4.76 KB	-rw-rw-r--	2024-05-22 12:36
auth.php	4.39 KB	-rw-rw-r--	2024-05-22 12:36
broadcasting.php	2.12 KB	-rw-rw-r--	2024-05-30 15:01
cache.php	3.35 KB	-rw-rw-r--	2024-05-22 12:36
cors.php	846 B	-rw-rw-r--	2023-06-15 17:41
database.php	5.95 KB	-rw-rw-r--	2024-05-22 12:36
filesystems.php	2.31 KB	-rw-rw-r--	2024-05-22 12:36
hashing.php	1.54 KB	-rw-rw-r--	2023-06-15 17:41
image.php	508 B	-rw-rw-r--	2023-06-15 17:41
intended_routes.php	44 B	-rw-rw-r--	2024-05-22 12:36
logging.php	4.21 KB	-rw-rw-r--	2024-05-22 12:36
mail.php	3.15 KB	-rw-rw-r--	2024-05-22 12:36
queue.php	3.85 KB	-rw-rw-r--	2024-05-30 13:24
sanctum.php	2.24 KB	-rw-rw-r--	2023-06-15 17:41
services.php	973 B	-rw-rw-r--	2024-05-22 12:36
session.php	7.67 KB	-rw-rw-r--	2024-05-22 12:36
timezone.php	35 B	-rw-rw-r--	2025-11-28 17:14
view.php	1.03 KB	-rw-rw-r--	2023-06-15 17:41

Rename

<?php

return [

/*
    |--------------------------------------------------------------------------
    | Authentication Defaults
    |--------------------------------------------------------------------------
    |
    | This option defines the default authentication "guard" and password
    | reset "broker" for your application. You may change these values
    | as required, but they're a perfect start for most applications.
    |
    */

'defaults' => [
        'guard' => env('AUTH_GUARD', 'web'),
        'passwords' => env('AUTH_PASSWORD_BROKER', 'users'),
    ],

/*
    |--------------------------------------------------------------------------
    | Authentication Guards
    |--------------------------------------------------------------------------
    |
    | Next, you may define every authentication guard for your application.
    | Of course, a great default configuration has been defined for you
    | which utilizes session storage plus the Eloquent user provider.
    |
    | All authentication guards have a user provider, which defines how the
    | users are actually retrieved out of your database or other storage
    | system used by the application. Typically, Eloquent is utilized.
    |
    | Supported: "session"
    |
    */

'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
        'api' => [
            'driver' => 'session',
            'provider' => 'users',
            'hash' => true,
        ],

'admin' => [
            'driver' => 'session',
            'provider' => 'admins',
        ],
    ],

/*
    |--------------------------------------------------------------------------
    | User Providers
    |--------------------------------------------------------------------------
    |
    | All authentication guards have a user provider, which defines how the
    | users are actually retrieved out of your database or other storage
    | system used by the application. Typically, Eloquent is utilized.
    |
    | If you have multiple user tables or models you may configure multiple
    | providers to represent the model / table. These providers may then
    | be assigned to any extra authentication guards you have defined.
    |
    | Supported: "database", "eloquent"
    |
    */

'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\Models\User::class,
        ],
        'admins' => [
            'driver' => 'eloquent',
            'model' => App\Models\Admin::class,
        ],

// 'users' => [
        //     'driver' => 'database',
        //     'table' => 'users',
        // ],
    ],

/*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | These configuration options specify the behavior of Laravel's password
    | reset functionality, including the table utilized for token storage
    | and the user provider that is invoked to actually retrieve users.
    |
    | The expiry time is the number of minutes that each reset token will be
    | considered valid. This security feature keeps tokens short-lived so
    | they have less time to be guessed. You may change this as needed.
    |
    | The throttle setting is the number of seconds a user must wait before
    | generating more password reset tokens. This prevents the user from
    | quickly generating a very large amount of password reset tokens.
    |
    */

'passwords' => [
        'users' => [
            'provider' => 'users',
            'table' => 'password_reset_tokens',
            'expire' => 60,
            'throttle' => 60,
        ],
        'admins' => [
            'provider' => 'admins',
            'table' => 'admin_password_resets',
            'expire' => 60,
            'throttle' => 60,
        ],
    ],

/*
    |--------------------------------------------------------------------------
    | Password Confirmation Timeout
    |--------------------------------------------------------------------------
    |
    | Here you may define the amount of seconds before a password confirmation
    | window expires and users are asked to re-enter their password via the
    | confirmation screen. By default, the timeout lasts for three hours.
    |
    */

'password_timeout' => env('AUTH_PASSWORD_TIMEOUT', 10800),

];