hatame/hatame.andarza09
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git add .

Browse Source 
git commit  "create admin panel layout with header sidebar and footer"
This commit is contained in:
hatame
2026-08-18 09:49:19 +03:30
parent 14684d5537
commit d7bd95f71a
39 changed files with 347 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
config/auth.php
+7 -7
View File
@@ -25,9 +25,9 @@ return [
|
| 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.
| which utilizes session storage plus the Eloquent userController provider.
|
| All authentication guards have a user provider, which defines how the
| All authentication guards have a userController 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.
|
@@ -51,11 +51,11 @@ return [
| User Providers
|--------------------------------------------------------------------------
|
| All authentication guards have a user provider, which defines how the
| All authentication guards have a userController 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
| If you have multiple userController 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.
|
@@ -86,14 +86,14 @@ return [
|
| 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.
| and the userController 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
| The throttle setting is the number of seconds a userController must wait before
| generating more password reset tokens. This prevents the userController from
| quickly generating a very large amount of password reset tokens.
|
*/
config/models.php
+9 -9
View File
@@ -353,23 +353,23 @@ return [
| How the relations should be named in your models.
|
| 'related' Use the related table as the relation name.
| (post.author --> user.id)
generates Post::user() and User::posts()
| (post.author --> userController.id)
generates Post::userController() and User::posts()
|
| 'foreign_key' Use the foreign key as the relation name.
| This can help to provide more meaningful relationship names, and avoids naming conflicts
| if you have more than one relationship between two tables.
| (post.author_id --> user.id)
| (post.author_id --> userController.id)
| generates Post::author() and User::posts_where_author()
| (post.editor_id --> user.id)
| (post.editor_id --> userController.id)
| generates Post::editor() and User::posts_where_editor()
| ID suffixes can be omitted from foreign keys.
| (post.author --> user.id)
| (post.editor --> user.id)
| (post.author --> userController.id)
| (post.editor --> userController.id)
| generates the same as above.
| Where the foreign key matches the related table name, it behaves as per the 'related' strategy.
| (post.user_id --> user.id)
| generates Post::user() and User::posts()
| (post.user_id --> userController.id)
| generates Post::userController() and User::posts()
*/
'relation_name_strategy' => 'related',
@@ -486,7 +486,7 @@ return [
// 'except' => ['migrations'],
// 'only' => ['users'],
// // Table Specifics Bellow:
// 'user' => [
// 'userController' => [
// // Don't use any default trait
// 'use' => [],
// ]