add publish module

This commit is contained in:
Arno Kaimbacher 2018-08-29 17:18:15 +02:00
parent 100f6db9a6
commit ffbbc04206
93 changed files with 8150 additions and 10228 deletions

View file

@ -39,7 +39,7 @@ return [
|
*/
'debug' => env('APP_DEBUG', false),
'debug' => env('APP_DEBUG', true),
/*
|--------------------------------------------------------------------------
@ -178,7 +178,7 @@ return [
// List off others providers...
App\Providers\SolariumServiceProvider::class,
Spatie\Permission\PermissionServiceProvider::class,
Zizaco\Entrust\EntrustServiceProvider::class,
],

132
config/entrust.php Normal file
View file

@ -0,0 +1,132 @@
<?php
/**
* This file is part of Entrust,
* a role & permission management solution for Laravel.
*
* @license MIT
* @package Zizaco\Entrust
*/
return [
/*
|--------------------------------------------------------------------------
| Entrust Role Model
|--------------------------------------------------------------------------
|
| This is the Role model used by Entrust to create correct relations. Update
| the role if it is in a different namespace.
|
*/
'role' => 'App\Models\Role',
/*
|--------------------------------------------------------------------------
| Entrust Roles Table
|--------------------------------------------------------------------------
|
| This is the roles table used by Entrust to save roles to the database.
|
*/
'roles_table' => 'user_roles', //'roles',
/*
|--------------------------------------------------------------------------
| Entrust role foreign key
|--------------------------------------------------------------------------
|
| This is the role foreign key used by Entrust to make a proper
| relation between permissions and roles & roles and users
|
*/
'role_foreign_key' => 'role_id',
/*
|--------------------------------------------------------------------------
| Application User Model
|--------------------------------------------------------------------------
|
| This is the User model used by Entrust to create correct relations.
| Update the User if it is in a different namespace.
|
*/
'user' => 'App\User',
/*
|--------------------------------------------------------------------------
| Application Users Table
|--------------------------------------------------------------------------
|
| This is the users table used by the application to save users to the
| database.
|
*/
'users_table' => 'accounts', //'users',
/*
|--------------------------------------------------------------------------
| Entrust role_user Table
|--------------------------------------------------------------------------
|
| This is the role_user table used by Entrust to save assigned roles to the
| database.
|
*/
'role_user_table' => 'link_accounts_roles', //'role_user',
/*
|--------------------------------------------------------------------------
| Entrust user foreign key
|--------------------------------------------------------------------------
|
| This is the user foreign key used by Entrust to make a proper
| relation between roles and users
|
*/
'user_foreign_key' => 'account_id', //'user_id',
/*
|--------------------------------------------------------------------------
| Entrust Permission Model
|--------------------------------------------------------------------------
|
| This is the Permission model used by Entrust to create correct relations.
| Update the permission if it is in a different namespace.
|
*/
'permission' => 'App\Models\Permission',
/*
|--------------------------------------------------------------------------
| Entrust Permissions Table
|--------------------------------------------------------------------------
|
| This is the permissions table used by Entrust to save permissions to the
| database.
|
*/
'permissions_table' => 'permissions',
/*
|--------------------------------------------------------------------------
| Entrust permission_role Table
|--------------------------------------------------------------------------
|
| This is the permission_role table used by Entrust to save relationship
| between permissions and roles to the database.
|
*/
'permission_role_table' => 'role_has_permissions', //'permission_role',
/*
|--------------------------------------------------------------------------
| Entrust permission foreign key
|--------------------------------------------------------------------------
|
| This is the permission foreign key used by Entrust to make a proper
| relation between permissions and roles
|
*/
'permission_foreign_key' => 'permission_id',
];

View file

@ -6,15 +6,19 @@ return [
"accepted" => "accepted",
'submitted' => 'submitted',
'published' => 'published',
'updated' => 'updated'
'updated' => 'updated',
],
'server_states' => [
'server_states' => [
"audited" => "audited",
"published" => "published",
'restricted' => 'restricted',
'inprogress' => 'inprogress',
'unpublished' => 'unpublished',
'deleted' => 'deleted',
'temporary' => 'temporary'
]
'deleted' => 'deleted',
'temporary' => 'temporary',
],
'filetypes_allowed' => [
"pdf", "txt", "html", "htm", "png", "jpeg",
],
'max_filesize' => '2048',
];

View file

@ -1,92 +0,0 @@
<?php
return [
'models' => [
/*
* When using the "HasRoles" trait from this package, we need to know which
* Eloquent model should be used to retrieve your permissions. Of course, it
* is often just the "Permission" model but you may use whatever you like.
*
* The model you want to use as a Permission model needs to implement the
* `Spatie\Permission\Contracts\Permission` contract.
*/
'permission' => Spatie\Permission\Models\Permission::class,
/*
* When using the "HasRoles" trait from this package, we need to know which
* Eloquent model should be used to retrieve your roles. Of course, it
* is often just the "Role" model but you may use whatever you like.
*
* The model you want to use as a Role model needs to implement the
* `Spatie\Permission\Contracts\Role` contract.
*/
'role' => Spatie\Permission\Models\Role::class,
//'role' => App\Role::class,
],
'table_names' => [
/*
* When using the "HasRoles" trait from this package, we need to know which
* table should be used to retrieve your roles. We have chosen a basic
* default value but you may easily change it to any table you like.
*/
// 'roles' => 'roles',
'roles' => 'user_roles',
/*
* When using the "HasRoles" trait from this package, we need to know which
* table should be used to retrieve your permissions. We have chosen a basic
* default value but you may easily change it to any table you like.
*/
'permissions' => 'permissions',
/*
* When using the "HasRoles" trait from this package, we need to know which
* table should be used to retrieve your models permissions. We have chosen a
* basic default value but you may easily change it to any table you like.
*/
'model_has_permissions' => 'model_has_permissions',
/*
* When using the "HasRoles" trait from this package, we need to know which
* table should be used to retrieve your models roles. We have chosen a
* basic default value but you may easily change it to any table you like.
*/
// 'model_has_roles' => 'model_has_roles',
'model_has_roles' => 'link_accounts_roles',
/*
* When using the "HasRoles" trait from this package, we need to know which
* table should be used to retrieve your roles permissions. We have chosen a
* basic default value but you may easily change it to any table you like.
*/
'role_has_permissions' => 'role_has_permissions',
],
/*
* By default all permissions will be cached for 24 hours unless a permission or
* role is updated. Then the cache will be flushed immediately.
*/
'cache_expiration_time' => 60 * 24,
/*
* When set to true, the required permission/role names are added to the exception
* message. This could be considered an information leak in some contexts, so
* the default setting is false here for optimum safety.
*/
'display_permission_in_exception' => false,
];

View file

@ -14,7 +14,7 @@ return [
| Supported: "file", "cookie", "database", "apc",
| "memcached", "redis", "array"
|
*/
*/
'driver' => env('SESSION_DRIVER', 'file'),
@ -27,7 +27,7 @@ return [
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
*/
'lifetime' => 60,
// 120,
@ -43,7 +43,7 @@ return [
| should be encrypted before it is stored. All encryption will be run
| automatically by Laravel and you can use the Session like normal.
|
*/
*/
'encrypt' => false,
@ -56,9 +56,9 @@ return [
| files may be stored. A default has been set for you but a different
| location may be specified. This is only needed for file sessions.
|
*/
*/
'files' => storage_path().'/framework/sessions',
'files' => storage_path() . '/framework/sessions',
/*
|--------------------------------------------------------------------------
@ -69,7 +69,7 @@ return [
| connection that should be used to manage these sessions. This should
| correspond to a connection in your database configuration options.
|
*/
*/
'connection' => null,
@ -82,7 +82,7 @@ return [
| should use to manage the sessions. Of course, a sensible default is
| provided for you; however, you are free to change this as needed.
|
*/
*/
'table' => 'sessions',
@ -95,7 +95,7 @@ return [
| rid of old sessions from storage. Here are the chances that it will
| happen on a given request. By default, the odds are 2 out of 100.
|
*/
*/
'lottery' => [2, 100],
@ -108,7 +108,7 @@ return [
| instance by ID. The name specified here will get used every time a
| new session cookie is created by the framework for every driver.
|
*/
*/
'cookie' => 'laravel_session',
@ -121,7 +121,7 @@ return [
| be regarded as available. Typically, this will be the root path of
| your application but you are free to change this when necessary.
|
*/
*/
'path' => '/',
@ -134,7 +134,7 @@ return [
| in your application. This will determine which domains the cookie is
| available to in your application. A sensible default has been set.
|
*/
*/
'domain' => null,
@ -147,7 +147,7 @@ return [
| to the server if the browser has a HTTPS connection. This will keep
| the cookie from being sent to you if it can not be done securely.
|
*/
*/
'secure' => false,

View file

@ -11,11 +11,11 @@ return [
| an array of paths that should be checked for your views. Of course
| the usual Laravel view path has already been registered for you.
|
*/
*/
'paths' => [
// realpath(base_path('resources/views'))
resource_path('views')
resource_path('views'),
],
/*
@ -27,8 +27,8 @@ return [
| stored for your application. Typically, this is within the storage
| directory. However, as usual, you are free to change this value.
|
*/
*/
'compiled' => realpath(storage_path().'/framework/views'),
'compiled' => realpath(storage_path() . '/framework/views'),
];