parent
30eff3455e
commit
c22392bcc4
@ -1,31 +0,0 @@ |
||||
<?php |
||||
|
||||
namespace App\Providers; |
||||
|
||||
use Illuminate\Contracts\Auth\Access\Gate as GateContract; |
||||
use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider; |
||||
|
||||
class AuthServiceProvider extends ServiceProvider |
||||
{ |
||||
/** |
||||
* The policy mappings for the application. |
||||
* |
||||
* @var array |
||||
*/ |
||||
protected $policies = [ |
||||
'App\Model' => 'App\Policies\ModelPolicy', |
||||
]; |
||||
|
||||
/** |
||||
* Register any application authentication / authorization services. |
||||
* |
||||
* @param \Illuminate\Contracts\Auth\Access\Gate $gate |
||||
* @return void |
||||
*/ |
||||
public function boot(GateContract $gate) |
||||
{ |
||||
$this->registerPolicies($gate); |
||||
|
||||
// |
||||
} |
||||
} |
@ -1,107 +0,0 @@ |
||||
<?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", "token" |
||||
| |
||||
*/ |
||||
|
||||
'guards' => [ |
||||
'web' => [ |
||||
'driver' => 'session', |
||||
'provider' => 'users', |
||||
], |
||||
|
||||
'api' => [ |
||||
'driver' => 'token', |
||||
'provider' => 'users', |
||||
], |
||||
], |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| 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\User::class, |
||||
], |
||||
|
||||
// 'users' => [ |
||||
// 'driver' => 'database', |
||||
// 'table' => 'users', |
||||
// ], |
||||
], |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Resetting Passwords |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may set the options for resetting passwords including the view |
||||
| that is your password reset e-mail. You may also set the name of the |
||||
| table that maintains all of the reset tokens for your application. |
||||
| |
||||
| 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', |
||||
'email' => 'auth.emails.password', |
||||
'table' => 'password_resets', |
||||
'expire' => 60, |
||||
], |
||||
], |
||||
|
||||
]; |
@ -1,52 +0,0 @@ |
||||
<?php |
||||
|
||||
return [ |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Default Broadcaster |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| This option controls the default broadcaster that will be used by the |
||||
| framework when an event needs to be broadcast. You may set this to |
||||
| any of the connections defined in the "connections" array below. |
||||
| |
||||
*/ |
||||
|
||||
'default' => env('BROADCAST_DRIVER', 'pusher'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Broadcast Connections |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may define all of the broadcast connections that will be used |
||||
| to broadcast events to other systems or over websockets. Samples of |
||||
| each available type of connection are provided inside this array. |
||||
| |
||||
*/ |
||||
|
||||
'connections' => [ |
||||
|
||||
'pusher' => [ |
||||
'driver' => 'pusher', |
||||
'key' => env('PUSHER_KEY'), |
||||
'secret' => env('PUSHER_SECRET'), |
||||
'app_id' => env('PUSHER_APP_ID'), |
||||
'options' => [ |
||||
// |
||||
], |
||||
], |
||||
|
||||
'redis' => [ |
||||
'driver' => 'redis', |
||||
'connection' => 'default', |
||||
], |
||||
|
||||
'log' => [ |
||||
'driver' => 'log', |
||||
], |
||||
|
||||
], |
||||
|
||||
]; |
@ -1,112 +0,0 @@ |
||||
<?php |
||||
|
||||
return [ |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Mail Driver |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Laravel supports both SMTP and PHP's "mail" function as drivers for the |
||||
| sending of e-mail. You may specify which one you're using throughout |
||||
| your application here. By default, Laravel is setup for SMTP mail. |
||||
| |
||||
| Supported: "smtp", "mail", "sendmail", "mailgun", "mandrill", |
||||
| "ses", "sparkpost", "log" |
||||
| |
||||
*/ |
||||
|
||||
'driver' => env('MAIL_DRIVER', 'smtp'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| SMTP Host Address |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may provide the host address of the SMTP server used by your |
||||
| applications. A default option is provided that is compatible with |
||||
| the Mailgun mail service which will provide reliable deliveries. |
||||
| |
||||
*/ |
||||
|
||||
'host' => env('MAIL_HOST', 'smtp.mailgun.org'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| SMTP Host Port |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| This is the SMTP port used by your application to deliver e-mails to |
||||
| users of the application. Like the host we have set this value to |
||||
| stay compatible with the Mailgun e-mail application by default. |
||||
| |
||||
*/ |
||||
|
||||
'port' => env('MAIL_PORT', 587), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Global "From" Address |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| You may wish for all e-mails sent by your application to be sent from |
||||
| the same address. Here, you may specify a name and address that is |
||||
| used globally for all e-mails that are sent by your application. |
||||
| |
||||
*/ |
||||
|
||||
'from' => ['address' => null, 'name' => null], |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| E-Mail Encryption Protocol |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may specify the encryption protocol that should be used when |
||||
| the application send e-mail messages. A sensible default using the |
||||
| transport layer security protocol should provide great security. |
||||
| |
||||
*/ |
||||
|
||||
'encryption' => env('MAIL_ENCRYPTION', 'tls'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| SMTP Server Username |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| If your SMTP server requires a username for authentication, you should |
||||
| set it here. This will get used to authenticate with your server on |
||||
| connection. You may also set the "password" value below this one. |
||||
| |
||||
*/ |
||||
|
||||
'username' => env('MAIL_USERNAME'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| SMTP Server Password |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may set the password required by your SMTP server to send out |
||||
| messages from your application. This will be given to the server on |
||||
| connection so that the application will be able to send messages. |
||||
| |
||||
*/ |
||||
|
||||
'password' => env('MAIL_PASSWORD'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Sendmail System Path |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| When using the "sendmail" driver to send e-mails, we will need to know |
||||
| the path to where Sendmail lives on this server. A default path has |
||||
| been provided here, which will work well on most of your systems. |
||||
| |
||||
*/ |
||||
|
||||
'sendmail' => '/usr/sbin/sendmail -bs', |
||||
|
||||
]; |
@ -1,85 +0,0 @@ |
||||
<?php |
||||
|
||||
return [ |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Default Queue Driver |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| The Laravel queue API supports a variety of back-ends via an unified |
||||
| API, giving you convenient access to each back-end using the same |
||||
| syntax for each one. Here you may set the default queue driver. |
||||
| |
||||
| Supported: "null", "sync", "database", "beanstalkd", "sqs", "redis" |
||||
| |
||||
*/ |
||||
|
||||
'default' => env('QUEUE_DRIVER', 'sync'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Queue Connections |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may configure the connection information for each server that |
||||
| is used by your application. A default configuration has been added |
||||
| for each back-end shipped with Laravel. You are free to add more. |
||||
| |
||||
*/ |
||||
|
||||
'connections' => [ |
||||
|
||||
'sync' => [ |
||||
'driver' => 'sync', |
||||
], |
||||
|
||||
'database' => [ |
||||
'driver' => 'database', |
||||
'table' => 'jobs', |
||||
'queue' => 'default', |
||||
'expire' => 60, |
||||
], |
||||
|
||||
'beanstalkd' => [ |
||||
'driver' => 'beanstalkd', |
||||
'host' => 'localhost', |
||||
'queue' => 'default', |
||||
'ttr' => 60, |
||||
], |
||||
|
||||
'sqs' => [ |
||||
'driver' => 'sqs', |
||||
'key' => 'your-public-key', |
||||
'secret' => 'your-secret-key', |
||||
'prefix' => 'https://sqs.us-east-1.amazonaws.com/your-account-id', |
||||
'queue' => 'your-queue-name', |
||||
'region' => 'us-east-1', |
||||
], |
||||
|
||||
'redis' => [ |
||||
'driver' => 'redis', |
||||
'connection' => 'default', |
||||
'queue' => 'default', |
||||
'expire' => 60, |
||||
], |
||||
|
||||
], |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Failed Queue Jobs |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| These options configure the behavior of failed queue job logging so you |
||||
| can control which database and table are used to store the jobs that |
||||
| have failed. You may change them to any database / table you wish. |
||||
| |
||||
*/ |
||||
|
||||
'failed' => [ |
||||
'database' => env('DB_CONNECTION', 'mysql'), |
||||
'table' => 'failed_jobs', |
||||
], |
||||
|
||||
]; |
@ -1,38 +0,0 @@ |
||||
<?php |
||||
|
||||
return [ |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Third Party Services |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| This file is for storing the credentials for third party services such |
||||
| as Stripe, Mailgun, Mandrill, and others. This file provides a sane |
||||
| default location for this type of information, allowing packages |
||||
| to have a conventional place to find your various credentials. |
||||
| |
||||
*/ |
||||
|
||||
'mailgun' => [ |
||||
'domain' => env('MAILGUN_DOMAIN'), |
||||
'secret' => env('MAILGUN_SECRET'), |
||||
], |
||||
|
||||
'ses' => [ |
||||
'key' => env('SES_KEY'), |
||||
'secret' => env('SES_SECRET'), |
||||
'region' => 'us-east-1', |
||||
], |
||||
|
||||
'sparkpost' => [ |
||||
'secret' => env('SPARKPOST_SECRET'), |
||||
], |
||||
|
||||
'stripe' => [ |
||||
'model' => App\User::class, |
||||
'key' => env('STRIPE_KEY'), |
||||
'secret' => env('STRIPE_SECRET'), |
||||
], |
||||
|
||||
]; |
@ -1,166 +0,0 @@ |
||||
<?php |
||||
|
||||
return [ |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Default Session Driver |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| This option controls the default session "driver" that will be used on |
||||
| requests. By default, we will use the lightweight native driver but |
||||
| you may specify any of the other wonderful drivers provided here. |
||||
| |
||||
| Supported: "file", "cookie", "database", "apc", |
||||
| "memcached", "redis", "array" |
||||
| |
||||
*/ |
||||
|
||||
'driver' => env('SESSION_DRIVER', 'file'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Lifetime |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may specify the number of minutes that you wish the session |
||||
| to be allowed to remain idle before it expires. If you want them |
||||
| to immediately expire on the browser closing, set that option. |
||||
| |
||||
*/ |
||||
|
||||
'lifetime' => 120, |
||||
|
||||
'expire_on_close' => false, |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Encryption |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| This option allows you to easily specify that all of your session data |
||||
| 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, |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session File Location |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| When using the native session driver, we need a location where session |
||||
| 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'), |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Database Connection |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| When using the "database" or "redis" session drivers, you may specify a |
||||
| connection that should be used to manage these sessions. This should |
||||
| correspond to a connection in your database configuration options. |
||||
| |
||||
*/ |
||||
|
||||
'connection' => null, |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Database Table |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| When using the "database" session driver, you may specify the table we |
||||
| 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', |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Sweeping Lottery |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Some session drivers must manually sweep their storage location to get |
||||
| 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], |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Cookie Name |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may change the name of the cookie used to identify a session |
||||
| 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', |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Cookie Path |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| The session cookie path determines the path for which the cookie will |
||||
| be regarded as available. Typically, this will be the root path of |
||||
| your application but you are free to change this when necessary. |
||||
| |
||||
*/ |
||||
|
||||
'path' => '/', |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| Session Cookie Domain |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Here you may change the domain of the cookie used to identify a session |
||||
| in your application. This will determine which domains the cookie is |
||||
| available to in your application. A sensible default has been set. |
||||
| |
||||
*/ |
||||
|
||||
'domain' => null, |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| HTTPS Only Cookies |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| By setting this option to true, session cookies will only be sent back |
||||
| 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, |
||||
|
||||
/* |
||||
|-------------------------------------------------------------------------- |
||||
| HTTP Access Only |
||||
|-------------------------------------------------------------------------- |
||||
| |
||||
| Setting this value to true will prevent JavaScript from accessing the |
||||
| value of the cookie and the cookie will only be accessible through |
||||
| the HTTP protocol. You are free to modify this option if needed. |
||||
| |
||||
*/ |
||||
|
||||
'http_only' => true, |
||||
|
||||
]; |
Loading…
Reference in new issue