mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
50c8033099
* Shift HTTP kernel and middleware * Shift service providers * Shift console routes * Shift to class based factories * Namespace seeders * Shift PSR-4 autoloading * Default config files In an effort to make upgrading the constantly changing config files easier, Shift defaulted them. This allows you to review the commit diff for once for customizations when you are done Shifting. Moving forward, consider using ENV variables or create a separate config file to allow the core config files to remain as default as possible. * Shift Laravel dependencies * Shift return type of base TestCase methods From the [PHPUnit 8 release notes][1], the `TestCase` methods below now declare a `void` return type: - `setUpBeforeClass()` - `setUp()` - `assertPreConditions()` - `assertPostConditions()` - `tearDown()` - `tearDownAfterClass()` - `onNotSuccessfulTest()` [1]: https://phpunit.de/announcements/phpunit-8.html * Shift cleanup * console routes * composer update * factories * phpunit * bootstrap pagination * model factory * wip * Apply fixes from StyleCI (#12236) * wip * Apply fixes from StyleCI (#12238) * wip * wip * wip * wip * Apply fixes from StyleCI (#12240) * wip * Apply fixes from StyleCI (#12242) * composer update * Bump to PHP 7.3 minimum Co-authored-by: Laravel Shift <shift@laravelshift.com>
137 lines
4.3 KiB
PHP
137 lines
4.3 KiB
PHP
<?php
|
|
|
|
/*
|
|
| !!!! DO NOT EDIT THIS FILE !!!!
|
|
|
|
|
| You can change settings by setting them in the environment or .env
|
|
| If there is something you need to change, but is not available as an environment setting,
|
|
| request an environment variable to be created upstream or send a pull request.
|
|
*/
|
|
|
|
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", "token"
|
|
|
|
|
*/
|
|
|
|
'guards' => [
|
|
'web' => [
|
|
'driver' => 'session',
|
|
'provider' => 'legacy',
|
|
],
|
|
|
|
'api' => [
|
|
'driver' => 'token',
|
|
'provider' => 'users',
|
|
'hash' => false,
|
|
],
|
|
|
|
'token' => [
|
|
'driver' => 'token_driver',
|
|
'provider' => 'token_provider',
|
|
'hash' => false,
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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,
|
|
],
|
|
|
|
'legacy' => [
|
|
'driver' => 'legacy',
|
|
'model' => App\Models\User::class,
|
|
],
|
|
|
|
// '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 the reset token should 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,
|
|
|
|
];
|