AI store generator for ecommerce, Malaysia first. Laravel 13 + React + TypeScript.
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

fortify.php 5.2KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  1. <?php
  2. use Laravel\Fortify\Features;
  3. return [
  4. /*
  5. |--------------------------------------------------------------------------
  6. | Fortify Guard
  7. |--------------------------------------------------------------------------
  8. |
  9. | Here you may specify which authentication guard Fortify will use while
  10. | authenticating users. This value should correspond with one of your
  11. | guards that is already present in your "auth" configuration file.
  12. |
  13. */
  14. 'guard' => 'web',
  15. /*
  16. |--------------------------------------------------------------------------
  17. | Fortify Password Broker
  18. |--------------------------------------------------------------------------
  19. |
  20. | Here you may specify which password broker Fortify can use when a user
  21. | is resetting their password. This configured value should match one
  22. | of your password brokers setup in your "auth" configuration file.
  23. |
  24. */
  25. 'passwords' => 'users',
  26. /*
  27. |--------------------------------------------------------------------------
  28. | Username / Email
  29. |--------------------------------------------------------------------------
  30. |
  31. | This value defines which model attribute should be considered as your
  32. | application's "username" field. Typically, this might be the email
  33. | address of the users but you are free to change this value here.
  34. |
  35. | Out of the box, Fortify expects forgot password and reset password
  36. | requests to have a field named 'email'. If the application uses
  37. | another name for the field you may define it below as needed.
  38. |
  39. */
  40. 'username' => 'email',
  41. 'email' => 'email',
  42. /*
  43. |--------------------------------------------------------------------------
  44. | Lowercase Usernames
  45. |--------------------------------------------------------------------------
  46. |
  47. | This value defines whether usernames should be lowercased before saving
  48. | them in the database, as some database system string fields are case
  49. | sensitive. You may disable this for your application if necessary.
  50. |
  51. */
  52. 'lowercase_usernames' => true,
  53. /*
  54. |--------------------------------------------------------------------------
  55. | Home Path
  56. |--------------------------------------------------------------------------
  57. |
  58. | Here you may configure the path where users will get redirected during
  59. | authentication or password reset when the operations are successful
  60. | and the user is authenticated. You are free to change this value.
  61. |
  62. */
  63. 'home' => '/dashboard',
  64. /*
  65. |--------------------------------------------------------------------------
  66. | Fortify Routes Prefix / Subdomain
  67. |--------------------------------------------------------------------------
  68. |
  69. | Here you may specify which prefix Fortify will assign to all the routes
  70. | that it registers with the application. If necessary, you may change
  71. | subdomain under which all of the Fortify routes will be available.
  72. |
  73. */
  74. 'prefix' => '',
  75. 'domain' => null,
  76. /*
  77. |--------------------------------------------------------------------------
  78. | Fortify Routes Middleware
  79. |--------------------------------------------------------------------------
  80. |
  81. | Here you may specify which middleware Fortify will assign to the routes
  82. | that it registers with the application. If necessary, you may change
  83. | these middleware but typically this provided default is preferred.
  84. |
  85. */
  86. 'middleware' => ['web'],
  87. /*
  88. |--------------------------------------------------------------------------
  89. | Rate Limiting
  90. |--------------------------------------------------------------------------
  91. |
  92. | By default, Fortify will throttle logins to five requests per minute for
  93. | every email and IP address combination. However, if you would like to
  94. | specify a custom rate limiter to call then you may specify it here.
  95. |
  96. */
  97. 'limiters' => [
  98. 'login' => 'login',
  99. 'two-factor' => 'two-factor',
  100. ],
  101. /*
  102. |--------------------------------------------------------------------------
  103. | Register View Routes
  104. |--------------------------------------------------------------------------
  105. |
  106. | Here you may specify if the routes returning views should be disabled as
  107. | you may not need them when building your own application. This may be
  108. | especially true if you're writing a custom single-page application.
  109. |
  110. */
  111. 'views' => true,
  112. /*
  113. |--------------------------------------------------------------------------
  114. | Features
  115. |--------------------------------------------------------------------------
  116. |
  117. | Some of the Fortify features are optional. You may disable the features
  118. | by removing them from this array. You're free to only remove some of
  119. | these features, or you can even remove all of these if you need to.
  120. |
  121. */
  122. 'features' => [
  123. Features::registration(),
  124. Features::resetPasswords(),
  125. Features::emailVerification(),
  126. Features::twoFactorAuthentication([
  127. 'confirm' => true,
  128. 'confirmPassword' => true,
  129. // 'window' => 0
  130. ]),
  131. ],
  132. ];