File Manager Lite
Dir:
/home/u540325668/domains/sostabazar.in/public_html/schooldemo/config
Upload
[..]
auth.php (3.92 KB)
Edit
Rename
Del
broadcasting.php (1.82 KB)
Edit
Rename
Del
dompdf.php (11.21 KB)
Edit
Rename
Del
excel.php (12.09 KB)
Edit
Rename
Del
hashing.php (1.54 KB)
Edit
Rename
Del
image.php (508 B)
Edit
Rename
Del
installer.php (2.63 KB)
Edit
Rename
Del
logging.php (3.61 KB)
Edit
Rename
Del
mail.php (3.53 KB)
Edit
Rename
Del
sanctum.php (2.24 KB)
Edit
Rename
Del
session.php (6.86 KB)
Edit
Rename
Del
Edit: auth.php
<?php return [ /* |-------------------------------------------------------------------------- | Authentication Defaults |-------------------------------------------------------------------------- | | This option controls the default authentication "guard" and password | reset options for your application. You may change these defaults | as required, but they're a perfect start for most applications. | */ 'defaults' => [ 'guard' => 'web', 'passwords' => 'users', ], /* |-------------------------------------------------------------------------- | Authentication Guards |-------------------------------------------------------------------------- | | Next, you may define every authentication guard for your application. | Of course, a great default configuration has been defined for you | here which uses session storage and the Eloquent user provider. | | All authentication drivers have a user provider. This defines how the | users are actually retrieved out of your database or other storage | mechanisms used by this application to persist your user's data. | | Supported: "session" | */ 'guards' => [ 'web' => [ 'driver' => 'session', 'provider' => 'users', ], 'school_web' => [ 'driver' => 'session', 'provider' => 'school_users', // Reference to a custom provider ], ], /* |-------------------------------------------------------------------------- | User Providers |-------------------------------------------------------------------------- | | All authentication drivers have a user provider. This defines how the | users are actually retrieved out of your database or other storage | 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" | */ 'providers' => [ 'users' => [ 'driver' => 'eloquent', 'model' => App\Models\User::class, ], 'school_users' => [ 'driver' => 'eloquent', 'model' => App\Models\User::class, 'connection' => 'school', // Dynamic connection for school databases ], // 'users' => [ // 'driver' => 'database', // 'table' => 'users', // ], ], /* |-------------------------------------------------------------------------- | Resetting Passwords |-------------------------------------------------------------------------- | | You may specify multiple password reset configurations if you have more | than one user table or model in the application and you want to have | separate password reset settings based on the specific user types. | | The expire 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. | */ 'passwords' => [ 'users' => [ 'provider' => 'users', 'table' => 'password_resets', 'expire' => 60, 'throttle' => 60, ], ], /* |-------------------------------------------------------------------------- | Password Confirmation Timeout |-------------------------------------------------------------------------- | | Here you may define the amount of seconds before a password confirmation | times out and the user is prompted to re-enter their password via the | confirmation screen. By default, the timeout lasts for three hours. | */ 'password_timeout' => 10800, ];
Simpan