├── .editorconfig ├── .env.example ├── .gitattributes ├── .gitignore ├── .styleci.yml ├── README.md ├── app ├── ApiCode.php ├── Console │ └── Kernel.php ├── Exceptions │ └── Handler.php ├── Http │ ├── Controllers │ │ ├── AuthController.php │ │ ├── Controller.php │ │ ├── ForgotPasswordController.php │ │ ├── RegistrationController.php │ │ ├── UserController.php │ │ └── VerificationController.php │ ├── Kernel.php │ ├── Middleware │ │ ├── Authenticate.php │ │ ├── CheckForMaintenanceMode.php │ │ ├── EncryptCookies.php │ │ ├── LogRoute.php │ │ ├── RedirectIfAuthenticated.php │ │ ├── TrimStrings.php │ │ ├── TrustProxies.php │ │ └── VerifyCsrfToken.php │ └── Requests │ │ ├── RegistrationRequest.php │ │ └── ResetPasswordRequest.php ├── Providers │ ├── AppServiceProvider.php │ ├── AuthServiceProvider.php │ ├── BroadcastServiceProvider.php │ ├── EventServiceProvider.php │ ├── RouteServiceProvider.php │ └── TelescopeServiceProvider.php └── User.php ├── artisan ├── bootstrap ├── app.php └── cache │ └── .gitignore ├── composer.json ├── composer.lock ├── config ├── app.php ├── auth.php ├── backup.php ├── broadcasting.php ├── cache.php ├── cors.php ├── database.php ├── filesystems.php ├── hashing.php ├── jwt.php ├── logging.php ├── mail.php ├── queue.php ├── response_builder.php ├── services.php ├── session.php ├── telescope.php └── view.php ├── database ├── .gitignore ├── factories │ └── UserFactory.php ├── migrations │ ├── 2014_10_12_000000_create_users_table.php │ └── 2019_08_19_000000_create_failed_jobs_table.php └── seeds │ ├── DatabaseSeeder.php │ └── UsersTableSeeder.php ├── package.json ├── phpunit.xml ├── public ├── .htaccess ├── favicon.ico ├── index.php ├── robots.txt ├── vendor │ └── telescope │ │ ├── app-dark.css │ │ ├── app.css │ │ ├── app.js │ │ ├── favicon.ico │ │ └── mix-manifest.json └── web.config ├── resources ├── js │ ├── app.js │ └── bootstrap.js ├── lang │ ├── en │ │ ├── api.php │ │ ├── auth.php │ │ ├── pagination.php │ │ ├── passwords.php │ │ └── validation.php │ └── vendor │ │ └── backup │ │ ├── ar │ │ └── notifications.php │ │ ├── cs │ │ └── notifications.php │ │ ├── da │ │ └── notifications.php │ │ ├── de │ │ └── notifications.php │ │ ├── en │ │ └── notifications.php │ │ ├── es │ │ └── notifications.php │ │ ├── fa │ │ └── notifications.php │ │ ├── fi │ │ └── notifications.php │ │ ├── fr │ │ └── notifications.php │ │ ├── hi │ │ └── notifications.php │ │ ├── id │ │ └── notifications.php │ │ ├── it │ │ └── notifications.php │ │ ├── nl │ │ └── notifications.php │ │ ├── pl │ │ └── notifications.php │ │ ├── pt-BR │ │ └── notifications.php │ │ ├── ro │ │ └── notifications.php │ │ ├── ru │ │ └── notifications.php │ │ ├── tr │ │ └── notifications.php │ │ ├── uk │ │ └── notifications.php │ │ ├── zh-CN │ │ └── notifications.php │ │ └── zh-TW │ │ └── notifications.php ├── sass │ └── app.scss └── views │ ├── auth │ └── reset_password.blade.php │ └── welcome.blade.php ├── routes ├── api.php ├── channels.php ├── console.php └── web.php ├── server.php ├── serverless.yml ├── storage ├── app │ ├── .gitignore │ └── public │ │ └── .gitignore ├── framework │ ├── .gitignore │ ├── cache │ │ ├── .gitignore │ │ └── data │ │ │ └── .gitignore │ ├── sessions │ │ └── .gitignore │ ├── testing │ │ └── .gitignore │ └── views │ │ └── .gitignore └── logs │ └── .gitignore ├── tests ├── CreatesApplication.php ├── Feature │ ├── ExampleTest.php │ └── UsersTest.php ├── TestCase.php └── Unit │ └── ExampleTest.php ├── webpack.mix.js └── worker.php /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | charset = utf-8 5 | end_of_line = lf 6 | insert_final_newline = true 7 | indent_style = space 8 | indent_size = 4 9 | trim_trailing_whitespace = true 10 | 11 | [*.md] 12 | trim_trailing_whitespace = false 13 | 14 | [*.{yml,yaml}] 15 | indent_size = 2 16 | -------------------------------------------------------------------------------- /.env.example: -------------------------------------------------------------------------------- 1 | APP_NAME=Laravel 2 | APP_ENV=local 3 | APP_KEY= 4 | APP_DEBUG=true 5 | APP_URL=http://localhost 6 | 7 | LOG_CHANNEL=stack 8 | 9 | DB_CONNECTION=mysql 10 | DB_HOST=127.0.0.1 11 | DB_PORT=3306 12 | DB_DATABASE=laravel 13 | DB_USERNAME=root 14 | DB_PASSWORD= 15 | 16 | BROADCAST_DRIVER=log 17 | QUEUE_CONNECTION=sync 18 | SESSION_DRIVER=file 19 | SESSION_LIFETIME=120 20 | 21 | REDIS_HOST=127.0.0.1 22 | REDIS_PASSWORD=null 23 | REDIS_PORT=6379 24 | 25 | MAIL_MAILER=smtp 26 | MAIL_HOST=smtp.mailtrap.io 27 | MAIL_PORT=2525 28 | MAIL_USERNAME=null 29 | MAIL_PASSWORD=null 30 | MAIL_ENCRYPTION=null 31 | MAIL_FROM_ADDRESS=null 32 | MAIL_FROM_NAME="${APP_NAME}" 33 | 34 | AWS_ACCESS_KEY_ID= 35 | AWS_SECRET_ACCESS_KEY= 36 | AWS_DEFAULT_REGION=us-east-1 37 | AWS_BUCKET= 38 | 39 | PUSHER_APP_ID= 40 | PUSHER_APP_KEY= 41 | PUSHER_APP_SECRET= 42 | PUSHER_APP_CLUSTER=mt1 43 | 44 | MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}" 45 | MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}" 46 | 47 | CACHE_DRIVER=array 48 | VIEW_COMPILED_PATH=/tmp/storage/framework/views 49 | SESSION_DRIVER=array 50 | LOG_CHANNEL=stderr 51 | -------------------------------------------------------------------------------- /.gitattributes: -------------------------------------------------------------------------------- 1 | * text=auto 2 | *.css linguist-vendored 3 | *.scss linguist-vendored 4 | *.js linguist-vendored 5 | CHANGELOG.md export-ignore 6 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | /node_modules 2 | /public/hot 3 | /public/storage 4 | /storage/*.key 5 | /vendor 6 | .env 7 | .env.backup 8 | .phpunit.result.cache 9 | Homestead.json 10 | Homestead.yaml 11 | npm-debug.log 12 | yarn-error.log 13 | /.idea 14 | /.serverless 15 | -------------------------------------------------------------------------------- /.styleci.yml: -------------------------------------------------------------------------------- 1 | php: 2 | preset: laravel 3 | disabled: 4 | - unused_use 5 | finder: 6 | not-name: 7 | - index.php 8 | - server.php 9 | js: 10 | finder: 11 | not-name: 12 | - webpack.mix.js 13 | css: true 14 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # About Laravel-Starter 2 | This Starter Application acts as starting point for application 3 | development. A lot of things which needs to be taken care of during REST API Development are already present here. 4 | 5 | ## How to deploy Serverless Laravel Application on AWS Lambda using bref? 6 | [![Deploy Serverless Laravel Application](https://img.youtube.com/vi/rWExnXzUBqc/0.jpg)](https://www.youtube.com/watch?v=rWExnXzUBqc) 7 | 8 | 9 | Following are the list of things taken care of: 10 | - JWT pre-installed 11 | - Authentication APIs are ready to use 12 | - Consistent Response in all APIs and Exception Handling 13 | - Registration API 14 | - Email Verification APIs 15 | - Forgot Password APIs 16 | - API Logging 17 | - Backup automation and management 18 | - Laravel Telescope for debugging in local environment 19 | - TDD (Test Driven Development) setup using phpunit 20 | 21 | ## Want to do it yourself? 22 | Here are the video tutorials you can follow to do it by yourself. 23 | 24 | | | | | 25 | |:-------------------------:|:-------------------------:|:-------------------------:| 26 | | Create a new Laravel Project| JWT installation and Setup| Auth APIs using JWT| 27 | | Consistent Response in REST APIs - Part I| Consistent Response in REST APIs - Part II| Registration API| 28 | | Email Verification APIs| Forgot Password APIs| API Logging Using middleware| 29 | | Backup automation and management|Laravel Telescope for debugging in local environment Laravel Telescope for debugging| TDD in Laravel using phpunit| 30 | 31 | 32 | ## Doing it on MacOS? 33 | Here is a simple video to setup Laravel application environment on MacOS using [Valet](https://laravel.com/docs/7.x/valet#introduction). 34 | 35 | [![Install Valet on Mac](https://img.youtube.com/vi/qN-QmeMm1vE/0.jpg)](https://www.youtube.com/watch?v=qN-QmeMm1vE) 36 | 37 | 38 | How to use? 39 | -- 40 | 41 | Clone this repository: 42 | 43 | git clone https://github.com/csinghdev/laravel-starter.git 44 | 45 | Remove .git folder since you want to create a new repository 46 | 47 | rm -rf .git 48 | 49 | Install dependencies: 50 | 51 | composer install 52 | 53 | Copy ``.env.example`` file: 54 | 55 | cp .env.example .env 56 | 57 | Configure ``.env`` file 58 | 59 | 60 | ## About Laravel 61 | 62 | Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel takes the pain out of development by easing common tasks used in many web projects, such as: 63 | 64 | - [Simple, fast routing engine](https://laravel.com/docs/routing). 65 | - [Powerful dependency injection container](https://laravel.com/docs/container). 66 | - Multiple back-ends for [session](https://laravel.com/docs/session) and [cache](https://laravel.com/docs/cache) storage. 67 | - Expressive, intuitive [database ORM](https://laravel.com/docs/eloquent). 68 | - Database agnostic [schema migrations](https://laravel.com/docs/migrations). 69 | - [Robust background job processing](https://laravel.com/docs/queues). 70 | - [Real-time event broadcasting](https://laravel.com/docs/broadcasting). 71 | 72 | Laravel is accessible, powerful, and provides tools required for large, robust applications. 73 | 74 | ## Learning Laravel 75 | 76 | Laravel has the most extensive and thorough [documentation](https://laravel.com/docs) and video tutorial library of all modern web application frameworks, making it a breeze to get started with the framework. 77 | 78 | If you don't feel like reading, [Laracasts](https://laracasts.com) can help. Laracasts contains over 1500 video tutorials on a range of topics including Laravel, modern PHP, unit testing, and JavaScript. Boost your skills by digging into our comprehensive video library. 79 | 80 | ## Laravel Sponsors 81 | 82 | We would like to extend our thanks to the following sponsors for funding Laravel development. If you are interested in becoming a sponsor, please visit the Laravel [Patreon page](https://patreon.com/taylorotwell). 83 | 84 | - **[Vehikl](https://vehikl.com/)** 85 | - **[Tighten Co.](https://tighten.co)** 86 | - **[Kirschbaum Development Group](https://kirschbaumdevelopment.com)** 87 | - **[64 Robots](https://64robots.com)** 88 | - **[Cubet Techno Labs](https://cubettech.com)** 89 | - **[Cyber-Duck](https://cyber-duck.co.uk)** 90 | - **[British Software Development](https://www.britishsoftware.co)** 91 | - **[Webdock, Fast VPS Hosting](https://www.webdock.io/en)** 92 | - **[DevSquad](https://devsquad.com)** 93 | - [UserInsights](https://userinsights.com) 94 | - [Fragrantica](https://www.fragrantica.com) 95 | - [SOFTonSOFA](https://softonsofa.com/) 96 | - [User10](https://user10.com) 97 | - [Soumettre.fr](https://soumettre.fr/) 98 | - [CodeBrisk](https://codebrisk.com) 99 | - [1Forge](https://1forge.com) 100 | - [TECPRESSO](https://tecpresso.co.jp/) 101 | - [Runtime Converter](http://runtimeconverter.com/) 102 | - [WebL'Agence](https://weblagence.com/) 103 | - [Invoice Ninja](https://www.invoiceninja.com) 104 | - [iMi digital](https://www.imi-digital.de/) 105 | - [Earthlink](https://www.earthlink.ro/) 106 | - [Steadfast Collective](https://steadfastcollective.com/) 107 | - [We Are The Robots Inc.](https://watr.mx/) 108 | - [Understand.io](https://www.understand.io/) 109 | - [Abdel Elrafa](https://abdelelrafa.com) 110 | - [Hyper Host](https://hyper.host) 111 | - [Appoly](https://www.appoly.co.uk) 112 | - [OP.GG](https://op.gg) 113 | - [云软科技](http://www.yunruan.ltd/) 114 | 115 | ## Contributing 116 | 117 | Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the [Laravel documentation](https://laravel.com/docs/contributions). 118 | 119 | ## Code of Conduct 120 | 121 | In order to ensure that the Laravel community is welcoming to all, please review and abide by the [Code of Conduct](https://laravel.com/docs/contributions#code-of-conduct). 122 | 123 | ## Security Vulnerabilities 124 | 125 | If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell via [taylor@laravel.com](mailto:taylor@laravel.com). All security vulnerabilities will be promptly addressed. 126 | 127 | ## License 128 | 129 | The Laravel framework is open-sourced software licensed under the [MIT license](https://opensource.org/licenses/MIT). 130 | -------------------------------------------------------------------------------- /app/ApiCode.php: -------------------------------------------------------------------------------- 1 | command('inspire')->hourly(); 28 | $schedule->command('backup:clean')->daily()->at('01:00'); 29 | $schedule->command('backup:run')->daily()->at('02:00'); 30 | } 31 | 32 | /** 33 | * Register the commands for the application. 34 | * 35 | * @return void 36 | */ 37 | protected function commands() 38 | { 39 | $this->load(__DIR__.'/Commands'); 40 | 41 | require base_path('routes/console.php'); 42 | } 43 | } 44 | -------------------------------------------------------------------------------- /app/Exceptions/Handler.php: -------------------------------------------------------------------------------- 1 | respondWithValidationError($exception); 58 | } 59 | 60 | return parent::render($request, $exception); 61 | } 62 | 63 | private function respondWithValidationError($exception) { 64 | return ResponseBuilder::asError(ApiCode::VALIDATION_ERROR) 65 | ->withData($exception->errors()) 66 | ->withHttpCode(422) 67 | ->build(); 68 | } 69 | } 70 | -------------------------------------------------------------------------------- /app/Http/Controllers/AuthController.php: -------------------------------------------------------------------------------- 1 | middleware('auth:api', ['except' => ['login']]); 13 | } 14 | 15 | public function login() { 16 | $credentials = request()->validate(['email' => 'required|email', 'password' => 'required|string|max:25']); 17 | 18 | if (! $token = auth()->attempt($credentials)) { 19 | return $this->respondUnAuthorizedRequest(ApiCode::INVALID_CREDENTIALS); 20 | } 21 | 22 | return $this->respondWithToken($token); 23 | } 24 | 25 | private function respondWithToken($token) { 26 | return $this->respond([ 27 | 'token' => $token, 28 | 'access_type' => 'bearer', 29 | 'expires_in' => auth()->factory()->getTTL() * 60 30 | ], "Login Successful"); 31 | } 32 | 33 | 34 | public function logout() { 35 | auth()->logout(); 36 | return $this->respondWithMessage('User successfully logged out'); 37 | } 38 | 39 | 40 | public function refresh() { 41 | return $this->respondWithToken(auth()->refresh()); 42 | } 43 | 44 | public function me() { 45 | return $this->respond(auth()->user()); 46 | } 47 | } 48 | -------------------------------------------------------------------------------- /app/Http/Controllers/Controller.php: -------------------------------------------------------------------------------- 1 | withData($data)->withMessage($msg)->build(); 18 | } 19 | 20 | public function respondWithMessage($msg) { 21 | return ResponseBuilder::asSuccess()->withMessage($msg)->build(); 22 | } 23 | 24 | public function respondWithError($api_code, $http_code) { 25 | return ResponseBuilder::asError($api_code)->withHttpCode($http_code)->build(); 26 | } 27 | 28 | public function respondBadRequest($api_code) { 29 | return $this->respondWithError($api_code, 400); 30 | } 31 | public function respondUnAuthorizedRequest($api_code) { 32 | return $this->respondWithError($api_code, 401); 33 | } 34 | public function respondNotFound($api_code) { 35 | return $this->respondWithError($api_code, 404); 36 | } 37 | } 38 | -------------------------------------------------------------------------------- /app/Http/Controllers/ForgotPasswordController.php: -------------------------------------------------------------------------------- 1 | validate(['email' => 'required|email']); 14 | 15 | Password::sendResetLink($credentials); 16 | 17 | return $this->respondWithMessage('Reset password link sent on your email id.'); 18 | } 19 | 20 | 21 | public function reset(ResetPasswordRequest $request) { 22 | $reset_password_status = Password::reset($request->validated(), function ($user, $password) { 23 | $user->password = $password; 24 | $user->save(); 25 | }); 26 | 27 | if ($reset_password_status == Password::INVALID_TOKEN) { 28 | return $this->respondBadRequest(ApiCode::INVALID_RESET_PASSWORD_TOKEN); 29 | } 30 | 31 | return $this->respondWithMessage("Password has been successfully changed"); 32 | } 33 | } 34 | -------------------------------------------------------------------------------- /app/Http/Controllers/RegistrationController.php: -------------------------------------------------------------------------------- 1 | getAttributes())->sendEmailVerificationNotification(); 18 | 19 | return $this->respondWithMessage('User successfully created'); 20 | } 21 | } 22 | -------------------------------------------------------------------------------- /app/Http/Controllers/UserController.php: -------------------------------------------------------------------------------- 1 | middleware('auth:api'); 11 | } 12 | 13 | public function updateProfile() { 14 | $attributes = request()->validate(['name' => 'nullable|string']); 15 | 16 | auth()->user()->update($attributes); 17 | 18 | return $this->respondWithMessage("User successfully updated"); 19 | } 20 | } 21 | -------------------------------------------------------------------------------- /app/Http/Controllers/VerificationController.php: -------------------------------------------------------------------------------- 1 | middleware('auth:api')->except(['verify']); 13 | } 14 | 15 | /** 16 | * Verify email 17 | * 18 | * @param $user_id 19 | * @param Request $request 20 | * @return \Illuminate\Http\RedirectResponse|\Symfony\Component\HttpFoundation\Response 21 | */ 22 | public function verify($user_id, Request $request) { 23 | if (! $request->hasValidSignature()) { 24 | return $this->respondUnAuthorizedRequest(ApiCode::INVALID_EMAIL_VERIFICATION_URL); 25 | } 26 | 27 | $user = User::findOrFail($user_id); 28 | 29 | if (!$user->hasVerifiedEmail()) { 30 | $user->markEmailAsVerified(); 31 | } 32 | 33 | return redirect()->to('/'); 34 | } 35 | 36 | /** 37 | * Resend email verification link 38 | * 39 | * @return \Symfony\Component\HttpFoundation\Response 40 | */ 41 | public function resend() { 42 | if (auth()->user()->hasVerifiedEmail()) { 43 | return $this->respondBadRequest(ApiCode::EMAIL_ALREADY_VERIFIED); 44 | } 45 | 46 | auth()->user()->sendEmailVerificationNotification(); 47 | 48 | return $this->respondWithMessage("Email verification link sent on your email id"); 49 | } 50 | } 51 | -------------------------------------------------------------------------------- /app/Http/Kernel.php: -------------------------------------------------------------------------------- 1 | [ 33 | \App\Http\Middleware\EncryptCookies::class, 34 | \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class, 35 | \Illuminate\Session\Middleware\StartSession::class, 36 | // \Illuminate\Session\Middleware\AuthenticateSession::class, 37 | \Illuminate\View\Middleware\ShareErrorsFromSession::class, 38 | \App\Http\Middleware\VerifyCsrfToken::class, 39 | \Illuminate\Routing\Middleware\SubstituteBindings::class, 40 | ], 41 | 42 | 'api' => [ 43 | 'throttle:60,1', 44 | \Illuminate\Routing\Middleware\SubstituteBindings::class, 45 | ], 46 | ]; 47 | 48 | /** 49 | * The application's route middleware. 50 | * 51 | * These middleware may be assigned to groups or used individually. 52 | * 53 | * @var array 54 | */ 55 | protected $routeMiddleware = [ 56 | 'auth' => \App\Http\Middleware\Authenticate::class, 57 | 'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class, 58 | 'bindings' => \Illuminate\Routing\Middleware\SubstituteBindings::class, 59 | 'cache.headers' => \Illuminate\Http\Middleware\SetCacheHeaders::class, 60 | 'can' => \Illuminate\Auth\Middleware\Authorize::class, 61 | 'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class, 62 | 'password.confirm' => \Illuminate\Auth\Middleware\RequirePassword::class, 63 | 'signed' => \Illuminate\Routing\Middleware\ValidateSignature::class, 64 | 'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class, 65 | 'verified' => \Illuminate\Auth\Middleware\EnsureEmailIsVerified::class, 66 | 'log.route' => LogRoute::class 67 | ]; 68 | } 69 | -------------------------------------------------------------------------------- /app/Http/Middleware/Authenticate.php: -------------------------------------------------------------------------------- 1 | expectsJson()) { 18 | return redirect(); 19 | } 20 | } 21 | } 22 | -------------------------------------------------------------------------------- /app/Http/Middleware/CheckForMaintenanceMode.php: -------------------------------------------------------------------------------- 1 | environment('local')) { 22 | $log = [ 23 | 'URI' => $request->getUri(), 24 | 'METHOD' => $request->getMethod(), 25 | 'REQUEST_BODY' => $request->all(), 26 | 'RESPONSE' => $response->getContent() 27 | ]; 28 | 29 | Log::info(json_encode($log)); 30 | } 31 | 32 | return $response; 33 | } 34 | } 35 | -------------------------------------------------------------------------------- /app/Http/Middleware/RedirectIfAuthenticated.php: -------------------------------------------------------------------------------- 1 | check()) { 22 | return redirect(RouteServiceProvider::HOME); 23 | } 24 | 25 | return $next($request); 26 | } 27 | } 28 | -------------------------------------------------------------------------------- /app/Http/Middleware/TrimStrings.php: -------------------------------------------------------------------------------- 1 | 'required|string', 28 | 'email' => 'required|email', 29 | 'password' => 'required|string|min:8|max:25', 30 | ]; 31 | } 32 | 33 | public function getAttributes() { 34 | return $this->validated(); 35 | } 36 | } 37 | -------------------------------------------------------------------------------- /app/Http/Requests/ResetPasswordRequest.php: -------------------------------------------------------------------------------- 1 | 'required|email', 28 | 'token' => 'required|string', 29 | 'password' => 'required|string|confirmed' 30 | ]; 31 | } 32 | } 33 | -------------------------------------------------------------------------------- /app/Providers/AppServiceProvider.php: -------------------------------------------------------------------------------- 1 | app->isLocal()) { 17 | $this->app->register(\Laravel\Telescope\TelescopeServiceProvider::class); 18 | $this->app->register(TelescopeServiceProvider::class); 19 | } 20 | } 21 | 22 | /** 23 | * Bootstrap any application services. 24 | * 25 | * @return void 26 | */ 27 | public function boot() 28 | { 29 | // Make sure the directory for compiled views exist 30 | if (! is_dir(config('view.compiled'))) { 31 | mkdir(config('view.compiled'), 0755, true); 32 | } 33 | } 34 | } 35 | -------------------------------------------------------------------------------- /app/Providers/AuthServiceProvider.php: -------------------------------------------------------------------------------- 1 | 'App\Policies\ModelPolicy', 17 | ]; 18 | 19 | /** 20 | * Register any authentication / authorization services. 21 | * 22 | * @return void 23 | */ 24 | public function boot() 25 | { 26 | $this->registerPolicies(); 27 | 28 | // 29 | } 30 | } 31 | -------------------------------------------------------------------------------- /app/Providers/BroadcastServiceProvider.php: -------------------------------------------------------------------------------- 1 | [ 19 | SendEmailVerificationNotification::class, 20 | ], 21 | ]; 22 | 23 | /** 24 | * Register any events for your application. 25 | * 26 | * @return void 27 | */ 28 | public function boot() 29 | { 30 | parent::boot(); 31 | 32 | // 33 | } 34 | } 35 | -------------------------------------------------------------------------------- /app/Providers/RouteServiceProvider.php: -------------------------------------------------------------------------------- 1 | mapApiRoutes(); 46 | 47 | $this->mapWebRoutes(); 48 | 49 | // 50 | } 51 | 52 | /** 53 | * Define the "web" routes for the application. 54 | * 55 | * These routes all receive session state, CSRF protection, etc. 56 | * 57 | * @return void 58 | */ 59 | protected function mapWebRoutes() 60 | { 61 | Route::middleware('web') 62 | ->namespace($this->namespace) 63 | ->group(base_path('routes/web.php')); 64 | } 65 | 66 | /** 67 | * Define the "api" routes for the application. 68 | * 69 | * These routes are typically stateless. 70 | * 71 | * @return void 72 | */ 73 | protected function mapApiRoutes() 74 | { 75 | Route::prefix('api') 76 | ->middleware('api') 77 | ->namespace($this->namespace) 78 | ->group(base_path('routes/api.php')); 79 | } 80 | } 81 | -------------------------------------------------------------------------------- /app/Providers/TelescopeServiceProvider.php: -------------------------------------------------------------------------------- 1 | hideSensitiveRequestDetails(); 22 | 23 | Telescope::filter(function (IncomingEntry $entry) { 24 | if ($this->app->environment('local')) { 25 | return true; 26 | } 27 | 28 | return $entry->isReportableException() || 29 | $entry->isFailedRequest() || 30 | $entry->isFailedJob() || 31 | $entry->isScheduledTask() || 32 | $entry->hasMonitoredTag(); 33 | }); 34 | } 35 | 36 | /** 37 | * Prevent sensitive request details from being logged by Telescope. 38 | * 39 | * @return void 40 | */ 41 | protected function hideSensitiveRequestDetails() 42 | { 43 | if ($this->app->environment('local')) { 44 | return; 45 | } 46 | 47 | Telescope::hideRequestParameters(['_token']); 48 | 49 | Telescope::hideRequestHeaders([ 50 | 'cookie', 51 | 'x-csrf-token', 52 | 'x-xsrf-token', 53 | ]); 54 | } 55 | 56 | /** 57 | * Register the Telescope gate. 58 | * 59 | * This gate determines who can access Telescope in non-local environments. 60 | * 61 | * @return void 62 | */ 63 | protected function gate() 64 | { 65 | Gate::define('viewTelescope', function ($user) { 66 | return in_array($user->email, [ 67 | // 68 | ]); 69 | }); 70 | } 71 | } 72 | -------------------------------------------------------------------------------- /app/User.php: -------------------------------------------------------------------------------- 1 | 'datetime', 40 | ]; 41 | 42 | /** 43 | * @inheritDoc 44 | */ 45 | public function getJWTIdentifier() 46 | { 47 | return $this->getKey(); 48 | } 49 | 50 | /** 51 | * @inheritDoc 52 | */ 53 | public function getJWTCustomClaims() 54 | { 55 | return []; 56 | } 57 | 58 | public function setPasswordAttribute($value) { 59 | $this->attributes['password'] = Hash::make($value); 60 | } 61 | } 62 | -------------------------------------------------------------------------------- /artisan: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env php 2 | make(Illuminate\Contracts\Console\Kernel::class); 34 | 35 | $status = $kernel->handle( 36 | $input = new Symfony\Component\Console\Input\ArgvInput, 37 | new Symfony\Component\Console\Output\ConsoleOutput 38 | ); 39 | 40 | /* 41 | |-------------------------------------------------------------------------- 42 | | Shutdown The Application 43 | |-------------------------------------------------------------------------- 44 | | 45 | | Once Artisan has finished running, we will fire off the shutdown events 46 | | so that any final work may be done by the application before we shut 47 | | down the process. This is the last thing to happen to the request. 48 | | 49 | */ 50 | 51 | $kernel->terminate($input, $status); 52 | 53 | exit($status); 54 | -------------------------------------------------------------------------------- /bootstrap/app.php: -------------------------------------------------------------------------------- 1 | singleton( 30 | Illuminate\Contracts\Http\Kernel::class, 31 | App\Http\Kernel::class 32 | ); 33 | 34 | $app->singleton( 35 | Illuminate\Contracts\Console\Kernel::class, 36 | App\Console\Kernel::class 37 | ); 38 | 39 | $app->singleton( 40 | Illuminate\Contracts\Debug\ExceptionHandler::class, 41 | App\Exceptions\Handler::class 42 | ); 43 | 44 | /* 45 | |-------------------------------------------------------------------------- 46 | | Return The Application 47 | |-------------------------------------------------------------------------- 48 | | 49 | | This script returns the application instance. The instance is given to 50 | | the calling script so we can separate the building of the instances 51 | | from the actual running of the application and sending responses. 52 | | 53 | */ 54 | 55 | return $app; 56 | -------------------------------------------------------------------------------- /bootstrap/cache/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /composer.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "laravel/laravel", 3 | "type": "project", 4 | "description": "The Laravel Framework.", 5 | "keywords": [ 6 | "framework", 7 | "laravel" 8 | ], 9 | "license": "MIT", 10 | "require": { 11 | "php": "^7.2.5", 12 | "bref/bref": "^0.5.29", 13 | "bref/laravel-bridge": "^0.2.0", 14 | "fideloper/proxy": "^4.2", 15 | "fruitcake/laravel-cors": "^1.0", 16 | "guzzlehttp/guzzle": "^6.3", 17 | "laravel/framework": "^7.0", 18 | "laravel/tinker": "^2.0", 19 | "marcin-orlowski/laravel-api-response-builder": "^7.1", 20 | "spatie/laravel-backup": "^6.9", 21 | "tymon/jwt-auth": "^1.0" 22 | }, 23 | "require-dev": { 24 | "facade/ignition": "^2.0", 25 | "fzaninotto/faker": "^1.9.1", 26 | "laravel/telescope": "^3.5", 27 | "mockery/mockery": "^1.3.1", 28 | "nunomaduro/collision": "^4.1", 29 | "phpunit/phpunit": "^8.5" 30 | }, 31 | "config": { 32 | "optimize-autoloader": true, 33 | "preferred-install": "dist", 34 | "sort-packages": true 35 | }, 36 | "extra": { 37 | "laravel": { 38 | "dont-discover": [ 39 | "laravel/telescope" 40 | ] 41 | } 42 | }, 43 | "autoload": { 44 | "psr-4": { 45 | "App\\": "app/" 46 | }, 47 | "classmap": [ 48 | "database/seeds", 49 | "database/factories" 50 | ] 51 | }, 52 | "autoload-dev": { 53 | "psr-4": { 54 | "Tests\\": "tests/" 55 | } 56 | }, 57 | "minimum-stability": "dev", 58 | "prefer-stable": true, 59 | "scripts": { 60 | "post-autoload-dump": [ 61 | "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", 62 | "@php artisan package:discover --ansi" 63 | ], 64 | "post-root-package-install": [ 65 | "@php -r \"file_exists('.env') || copy('.env.example', '.env');\"" 66 | ], 67 | "post-create-project-cmd": [ 68 | "@php artisan key:generate --ansi" 69 | ] 70 | } 71 | } 72 | -------------------------------------------------------------------------------- /config/app.php: -------------------------------------------------------------------------------- 1 | env('APP_NAME', 'Laravel'), 17 | 18 | /* 19 | |-------------------------------------------------------------------------- 20 | | Application Environment 21 | |-------------------------------------------------------------------------- 22 | | 23 | | This value determines the "environment" your application is currently 24 | | running in. This may determine how you prefer to configure various 25 | | services the application utilizes. Set this in your ".env" file. 26 | | 27 | */ 28 | 29 | 'env' => env('APP_ENV', 'production'), 30 | 31 | /* 32 | |-------------------------------------------------------------------------- 33 | | Application Debug Mode 34 | |-------------------------------------------------------------------------- 35 | | 36 | | When your application is in debug mode, detailed error messages with 37 | | stack traces will be shown on every error that occurs within your 38 | | application. If disabled, a simple generic error page is shown. 39 | | 40 | */ 41 | 42 | 'debug' => (bool) env('APP_DEBUG', false), 43 | 44 | /* 45 | |-------------------------------------------------------------------------- 46 | | Application URL 47 | |-------------------------------------------------------------------------- 48 | | 49 | | This URL is used by the console to properly generate URLs when using 50 | | the Artisan command line tool. You should set this to the root of 51 | | your application so that it is used when running Artisan tasks. 52 | | 53 | */ 54 | 55 | 'url' => env('APP_URL', 'http://localhost'), 56 | 57 | 'asset_url' => env('ASSET_URL', null), 58 | 59 | /* 60 | |-------------------------------------------------------------------------- 61 | | Application Timezone 62 | |-------------------------------------------------------------------------- 63 | | 64 | | Here you may specify the default timezone for your application, which 65 | | will be used by the PHP date and date-time functions. We have gone 66 | | ahead and set this to a sensible default for you out of the box. 67 | | 68 | */ 69 | 70 | 'timezone' => 'UTC', 71 | 72 | /* 73 | |-------------------------------------------------------------------------- 74 | | Application Locale Configuration 75 | |-------------------------------------------------------------------------- 76 | | 77 | | The application locale determines the default locale that will be used 78 | | by the translation service provider. You are free to set this value 79 | | to any of the locales which will be supported by the application. 80 | | 81 | */ 82 | 83 | 'locale' => 'en', 84 | 85 | /* 86 | |-------------------------------------------------------------------------- 87 | | Application Fallback Locale 88 | |-------------------------------------------------------------------------- 89 | | 90 | | The fallback locale determines the locale to use when the current one 91 | | is not available. You may change the value to correspond to any of 92 | | the language folders that are provided through your application. 93 | | 94 | */ 95 | 96 | 'fallback_locale' => 'en', 97 | 98 | /* 99 | |-------------------------------------------------------------------------- 100 | | Faker Locale 101 | |-------------------------------------------------------------------------- 102 | | 103 | | This locale will be used by the Faker PHP library when generating fake 104 | | data for your database seeds. For example, this will be used to get 105 | | localized telephone numbers, street address information and more. 106 | | 107 | */ 108 | 109 | 'faker_locale' => 'en_US', 110 | 111 | /* 112 | |-------------------------------------------------------------------------- 113 | | Encryption Key 114 | |-------------------------------------------------------------------------- 115 | | 116 | | This key is used by the Illuminate encrypter service and should be set 117 | | to a random, 32 character string, otherwise these encrypted strings 118 | | will not be safe. Please do this before deploying an application! 119 | | 120 | */ 121 | 122 | 'key' => env('APP_KEY'), 123 | 124 | 'cipher' => 'AES-256-CBC', 125 | 126 | /* 127 | |-------------------------------------------------------------------------- 128 | | Autoloaded Service Providers 129 | |-------------------------------------------------------------------------- 130 | | 131 | | The service providers listed here will be automatically loaded on the 132 | | request to your application. Feel free to add your own services to 133 | | this array to grant expanded functionality to your applications. 134 | | 135 | */ 136 | 137 | 'providers' => [ 138 | 139 | /* 140 | * Laravel Framework Service Providers... 141 | */ 142 | Illuminate\Auth\AuthServiceProvider::class, 143 | Illuminate\Broadcasting\BroadcastServiceProvider::class, 144 | Illuminate\Bus\BusServiceProvider::class, 145 | Illuminate\Cache\CacheServiceProvider::class, 146 | Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class, 147 | Illuminate\Cookie\CookieServiceProvider::class, 148 | Illuminate\Database\DatabaseServiceProvider::class, 149 | Illuminate\Encryption\EncryptionServiceProvider::class, 150 | Illuminate\Filesystem\FilesystemServiceProvider::class, 151 | Illuminate\Foundation\Providers\FoundationServiceProvider::class, 152 | Illuminate\Hashing\HashServiceProvider::class, 153 | Illuminate\Mail\MailServiceProvider::class, 154 | Illuminate\Notifications\NotificationServiceProvider::class, 155 | Illuminate\Pagination\PaginationServiceProvider::class, 156 | Illuminate\Pipeline\PipelineServiceProvider::class, 157 | Illuminate\Queue\QueueServiceProvider::class, 158 | Illuminate\Redis\RedisServiceProvider::class, 159 | Illuminate\Auth\Passwords\PasswordResetServiceProvider::class, 160 | Illuminate\Session\SessionServiceProvider::class, 161 | Illuminate\Translation\TranslationServiceProvider::class, 162 | Illuminate\Validation\ValidationServiceProvider::class, 163 | Illuminate\View\ViewServiceProvider::class, 164 | 165 | /* 166 | * Package Service Providers... 167 | */ 168 | 169 | /* 170 | * Application Service Providers... 171 | */ 172 | App\Providers\AppServiceProvider::class, 173 | App\Providers\AuthServiceProvider::class, 174 | // App\Providers\BroadcastServiceProvider::class, 175 | App\Providers\EventServiceProvider::class, 176 | App\Providers\RouteServiceProvider::class, 177 | 178 | ], 179 | 180 | /* 181 | |-------------------------------------------------------------------------- 182 | | Class Aliases 183 | |-------------------------------------------------------------------------- 184 | | 185 | | This array of class aliases will be registered when this application 186 | | is started. However, feel free to register as many as you wish as 187 | | the aliases are "lazy" loaded so they don't hinder performance. 188 | | 189 | */ 190 | 191 | 'aliases' => [ 192 | 193 | 'App' => Illuminate\Support\Facades\App::class, 194 | 'Arr' => Illuminate\Support\Arr::class, 195 | 'Artisan' => Illuminate\Support\Facades\Artisan::class, 196 | 'Auth' => Illuminate\Support\Facades\Auth::class, 197 | 'Blade' => Illuminate\Support\Facades\Blade::class, 198 | 'Broadcast' => Illuminate\Support\Facades\Broadcast::class, 199 | 'Bus' => Illuminate\Support\Facades\Bus::class, 200 | 'Cache' => Illuminate\Support\Facades\Cache::class, 201 | 'Config' => Illuminate\Support\Facades\Config::class, 202 | 'Cookie' => Illuminate\Support\Facades\Cookie::class, 203 | 'Crypt' => Illuminate\Support\Facades\Crypt::class, 204 | 'DB' => Illuminate\Support\Facades\DB::class, 205 | 'Eloquent' => Illuminate\Database\Eloquent\Model::class, 206 | 'Event' => Illuminate\Support\Facades\Event::class, 207 | 'File' => Illuminate\Support\Facades\File::class, 208 | 'Gate' => Illuminate\Support\Facades\Gate::class, 209 | 'Hash' => Illuminate\Support\Facades\Hash::class, 210 | 'Http' => Illuminate\Support\Facades\Http::class, 211 | 'Lang' => Illuminate\Support\Facades\Lang::class, 212 | 'Log' => Illuminate\Support\Facades\Log::class, 213 | 'Mail' => Illuminate\Support\Facades\Mail::class, 214 | 'Notification' => Illuminate\Support\Facades\Notification::class, 215 | 'Password' => Illuminate\Support\Facades\Password::class, 216 | 'Queue' => Illuminate\Support\Facades\Queue::class, 217 | 'Redirect' => Illuminate\Support\Facades\Redirect::class, 218 | 'Redis' => Illuminate\Support\Facades\Redis::class, 219 | 'Request' => Illuminate\Support\Facades\Request::class, 220 | 'Response' => Illuminate\Support\Facades\Response::class, 221 | 'Route' => Illuminate\Support\Facades\Route::class, 222 | 'Schema' => Illuminate\Support\Facades\Schema::class, 223 | 'Session' => Illuminate\Support\Facades\Session::class, 224 | 'Storage' => Illuminate\Support\Facades\Storage::class, 225 | 'Str' => Illuminate\Support\Str::class, 226 | 'URL' => Illuminate\Support\Facades\URL::class, 227 | 'Validator' => Illuminate\Support\Facades\Validator::class, 228 | 'View' => Illuminate\Support\Facades\View::class, 229 | 230 | ], 231 | 232 | ]; 233 | -------------------------------------------------------------------------------- /config/auth.php: -------------------------------------------------------------------------------- 1 | [ 17 | 'guard' => 'api', 18 | 'passwords' => 'users', 19 | ], 20 | 21 | /* 22 | |-------------------------------------------------------------------------- 23 | | Authentication Guards 24 | |-------------------------------------------------------------------------- 25 | | 26 | | Next, you may define every authentication guard for your application. 27 | | Of course, a great default configuration has been defined for you 28 | | here which uses session storage and the Eloquent user provider. 29 | | 30 | | All authentication drivers have a user provider. This defines how the 31 | | users are actually retrieved out of your database or other storage 32 | | mechanisms used by this application to persist your user's data. 33 | | 34 | | Supported: "session", "token" 35 | | 36 | */ 37 | 38 | 'guards' => [ 39 | 'web' => [ 40 | 'driver' => 'session', 41 | 'provider' => 'users', 42 | ], 43 | 44 | 'api' => [ 45 | 'driver' => 'jwt', 46 | 'provider' => 'users', 47 | 'hash' => false, 48 | ], 49 | ], 50 | 51 | /* 52 | |-------------------------------------------------------------------------- 53 | | User Providers 54 | |-------------------------------------------------------------------------- 55 | | 56 | | All authentication drivers have a user provider. This defines how the 57 | | users are actually retrieved out of your database or other storage 58 | | mechanisms used by this application to persist your user's data. 59 | | 60 | | If you have multiple user tables or models you may configure multiple 61 | | sources which represent each model / table. These sources may then 62 | | be assigned to any extra authentication guards you have defined. 63 | | 64 | | Supported: "database", "eloquent" 65 | | 66 | */ 67 | 68 | 'providers' => [ 69 | 'users' => [ 70 | 'driver' => 'eloquent', 71 | 'model' => App\User::class, 72 | ], 73 | 74 | // 'users' => [ 75 | // 'driver' => 'database', 76 | // 'table' => 'users', 77 | // ], 78 | ], 79 | 80 | /* 81 | |-------------------------------------------------------------------------- 82 | | Resetting Passwords 83 | |-------------------------------------------------------------------------- 84 | | 85 | | You may specify multiple password reset configurations if you have more 86 | | than one user table or model in the application and you want to have 87 | | separate password reset settings based on the specific user types. 88 | | 89 | | The expire time is the number of minutes that the reset token should be 90 | | considered valid. This security feature keeps tokens short-lived so 91 | | they have less time to be guessed. You may change this as needed. 92 | | 93 | */ 94 | 95 | 'passwords' => [ 96 | 'users' => [ 97 | 'provider' => 'users', 98 | 'table' => 'password_resets', 99 | 'expire' => 60, 100 | 'throttle' => 60, 101 | ], 102 | ], 103 | 104 | /* 105 | |-------------------------------------------------------------------------- 106 | | Password Confirmation Timeout 107 | |-------------------------------------------------------------------------- 108 | | 109 | | Here you may define the amount of seconds before a password confirmation 110 | | times out and the user is prompted to re-enter their password via the 111 | | confirmation screen. By default, the timeout lasts for three hours. 112 | | 113 | */ 114 | 115 | 'password_timeout' => 10800, 116 | 117 | ]; 118 | -------------------------------------------------------------------------------- /config/backup.php: -------------------------------------------------------------------------------- 1 | [ 6 | 7 | /* 8 | * The name of this application. You can use this name to monitor 9 | * the backups. 10 | */ 11 | 'name' => env('APP_NAME', 'laravel-backup'), 12 | 13 | 'source' => [ 14 | 15 | 'files' => [ 16 | 17 | /* 18 | * The list of directories and files that will be included in the backup. 19 | */ 20 | 'include' => [ 21 | base_path(), 22 | ], 23 | 24 | /* 25 | * These directories and files will be excluded from the backup. 26 | * 27 | * Directories used by the backup process will automatically be excluded. 28 | */ 29 | 'exclude' => [ 30 | base_path('vendor'), 31 | base_path('node_modules'), 32 | ], 33 | 34 | /* 35 | * Determines if symlinks should be followed. 36 | */ 37 | 'follow_links' => false, 38 | ], 39 | 40 | /* 41 | * The names of the connections to the databases that should be backed up 42 | * MySQL, PostgreSQL, SQLite and Mongo databases are supported. 43 | * 44 | * The content of the database dump may be customized for each connection 45 | * by adding a 'dump' key to the connection settings in config/database.php. 46 | * E.g. 47 | * 'mysql' => [ 48 | * ... 49 | * 'dump' => [ 50 | * 'excludeTables' => [ 51 | * 'table_to_exclude_from_backup', 52 | * 'another_table_to_exclude' 53 | * ] 54 | * ], 55 | * ], 56 | * 57 | * If you are using only InnoDB tables on a MySQL server, you can 58 | * also supply the useSingleTransaction option to avoid table locking. 59 | * 60 | * E.g. 61 | * 'mysql' => [ 62 | * ... 63 | * 'dump' => [ 64 | * 'useSingleTransaction' => true, 65 | * ], 66 | * ], 67 | * 68 | * For a complete list of available customization options, see https://github.com/spatie/db-dumper 69 | */ 70 | 'databases' => [ 71 | 'mysql', 72 | ], 73 | ], 74 | 75 | /* 76 | * The database dump can be compressed to decrease diskspace usage. 77 | * 78 | * Out of the box Laravel-backup supplies 79 | * Spatie\DbDumper\Compressors\GzipCompressor::class. 80 | * 81 | * You can also create custom compressor. More info on that here: 82 | * https://github.com/spatie/db-dumper#using-compression 83 | * 84 | * If you do not want any compressor at all, set it to null. 85 | */ 86 | 'database_dump_compressor' => Spatie\DbDumper\Compressors\GzipCompressor::class, 87 | 88 | 'destination' => [ 89 | 90 | /* 91 | * The filename prefix used for the backup zip file. 92 | */ 93 | 'filename_prefix' => '', 94 | 95 | /* 96 | * The disk names on which the backups will be stored. 97 | */ 98 | 'disks' => [ 99 | 'local', 100 | ], 101 | ], 102 | 103 | /* 104 | * The directory where the temporary files will be stored. 105 | */ 106 | 'temporary_directory' => storage_path('app/backup-temp'), 107 | ], 108 | 109 | /* 110 | * You can get notified when specific events occur. Out of the box you can use 'mail' and 'slack'. 111 | * For Slack you need to install guzzlehttp/guzzle and laravel/slack-notification-channel. 112 | * 113 | * You can also use your own notification classes, just make sure the class is named after one of 114 | * the `Spatie\Backup\Events` classes. 115 | */ 116 | 'notifications' => [ 117 | 118 | 'notifications' => [ 119 | \Spatie\Backup\Notifications\Notifications\BackupHasFailed::class => ['mail'], 120 | \Spatie\Backup\Notifications\Notifications\UnhealthyBackupWasFound::class => ['mail'], 121 | \Spatie\Backup\Notifications\Notifications\CleanupHasFailed::class => ['mail'], 122 | \Spatie\Backup\Notifications\Notifications\BackupWasSuccessful::class => ['mail'], 123 | \Spatie\Backup\Notifications\Notifications\HealthyBackupWasFound::class => ['mail'], 124 | \Spatie\Backup\Notifications\Notifications\CleanupWasSuccessful::class => ['mail'], 125 | ], 126 | 127 | /* 128 | * Here you can specify the notifiable to which the notifications should be sent. The default 129 | * notifiable will use the variables specified in this config file. 130 | */ 131 | 'notifiable' => \Spatie\Backup\Notifications\Notifiable::class, 132 | 133 | 'mail' => [ 134 | 'to' => 'chandresh@reportbugz.com', 135 | 136 | 'from' => [ 137 | 'address' => env('MAIL_FROM_ADDRESS', 'hello@reportbugz.com'), 138 | 'name' => env('MAIL_FROM_NAME', 'ReportBugz'), 139 | ], 140 | ], 141 | 142 | 'slack' => [ 143 | 'webhook_url' => '', 144 | 145 | /* 146 | * If this is set to null the default channel of the webhook will be used. 147 | */ 148 | 'channel' => null, 149 | 150 | 'username' => null, 151 | 152 | 'icon' => null, 153 | 154 | ], 155 | ], 156 | 157 | /* 158 | * Here you can specify which backups should be monitored. 159 | * If a backup does not meet the specified requirements the 160 | * UnHealthyBackupWasFound event will be fired. 161 | */ 162 | 'monitor_backups' => [ 163 | [ 164 | 'name' => env('APP_NAME', 'laravel-backup'), 165 | 'disks' => ['local'], 166 | 'health_checks' => [ 167 | \Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumAgeInDays::class => 1, 168 | \Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumStorageInMegabytes::class => 5000, 169 | ], 170 | ], 171 | 172 | /* 173 | [ 174 | 'name' => 'name of the second app', 175 | 'disks' => ['local', 's3'], 176 | 'health_checks' => [ 177 | \Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumAgeInDays::class => 1, 178 | \Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumStorageInMegabytes::class => 5000, 179 | ], 180 | ], 181 | */ 182 | ], 183 | 184 | 'cleanup' => [ 185 | /* 186 | * The strategy that will be used to cleanup old backups. The default strategy 187 | * will keep all backups for a certain amount of days. After that period only 188 | * a daily backup will be kept. After that period only weekly backups will 189 | * be kept and so on. 190 | * 191 | * No matter how you configure it the default strategy will never 192 | * delete the newest backup. 193 | */ 194 | 'strategy' => \Spatie\Backup\Tasks\Cleanup\Strategies\DefaultStrategy::class, 195 | 196 | 'default_strategy' => [ 197 | 198 | /* 199 | * The number of days for which backups must be kept. 200 | */ 201 | 'keep_all_backups_for_days' => 7, 202 | 203 | /* 204 | * The number of days for which daily backups must be kept. 205 | */ 206 | 'keep_daily_backups_for_days' => 16, 207 | 208 | /* 209 | * The number of weeks for which one weekly backup must be kept. 210 | */ 211 | 'keep_weekly_backups_for_weeks' => 8, 212 | 213 | /* 214 | * The number of months for which one monthly backup must be kept. 215 | */ 216 | 'keep_monthly_backups_for_months' => 4, 217 | 218 | /* 219 | * The number of years for which one yearly backup must be kept. 220 | */ 221 | 'keep_yearly_backups_for_years' => 2, 222 | 223 | /* 224 | * After cleaning up the backups remove the oldest backup until 225 | * this amount of megabytes has been reached. 226 | */ 227 | 'delete_oldest_backups_when_using_more_megabytes_than' => 5000, 228 | ], 229 | ], 230 | 231 | ]; 232 | -------------------------------------------------------------------------------- /config/broadcasting.php: -------------------------------------------------------------------------------- 1 | env('BROADCAST_DRIVER', 'null'), 19 | 20 | /* 21 | |-------------------------------------------------------------------------- 22 | | Broadcast Connections 23 | |-------------------------------------------------------------------------- 24 | | 25 | | Here you may define all of the broadcast connections that will be used 26 | | to broadcast events to other systems or over websockets. Samples of 27 | | each available type of connection are provided inside this array. 28 | | 29 | */ 30 | 31 | 'connections' => [ 32 | 33 | 'pusher' => [ 34 | 'driver' => 'pusher', 35 | 'key' => env('PUSHER_APP_KEY'), 36 | 'secret' => env('PUSHER_APP_SECRET'), 37 | 'app_id' => env('PUSHER_APP_ID'), 38 | 'options' => [ 39 | 'cluster' => env('PUSHER_APP_CLUSTER'), 40 | 'useTLS' => true, 41 | ], 42 | ], 43 | 44 | 'redis' => [ 45 | 'driver' => 'redis', 46 | 'connection' => 'default', 47 | ], 48 | 49 | 'log' => [ 50 | 'driver' => 'log', 51 | ], 52 | 53 | 'null' => [ 54 | 'driver' => 'null', 55 | ], 56 | 57 | ], 58 | 59 | ]; 60 | -------------------------------------------------------------------------------- /config/cache.php: -------------------------------------------------------------------------------- 1 | env('CACHE_DRIVER', 'file'), 22 | 23 | /* 24 | |-------------------------------------------------------------------------- 25 | | Cache Stores 26 | |-------------------------------------------------------------------------- 27 | | 28 | | Here you may define all of the cache "stores" for your application as 29 | | well as their drivers. You may even define multiple stores for the 30 | | same cache driver to group types of items stored in your caches. 31 | | 32 | */ 33 | 34 | 'stores' => [ 35 | 36 | 'apc' => [ 37 | 'driver' => 'apc', 38 | ], 39 | 40 | 'array' => [ 41 | 'driver' => 'array', 42 | 'serialize' => false, 43 | ], 44 | 45 | 'database' => [ 46 | 'driver' => 'database', 47 | 'table' => 'cache', 48 | 'connection' => null, 49 | ], 50 | 51 | 'file' => [ 52 | 'driver' => 'file', 53 | 'path' => storage_path('framework/cache/data'), 54 | ], 55 | 56 | 'memcached' => [ 57 | 'driver' => 'memcached', 58 | 'persistent_id' => env('MEMCACHED_PERSISTENT_ID'), 59 | 'sasl' => [ 60 | env('MEMCACHED_USERNAME'), 61 | env('MEMCACHED_PASSWORD'), 62 | ], 63 | 'options' => [ 64 | // Memcached::OPT_CONNECT_TIMEOUT => 2000, 65 | ], 66 | 'servers' => [ 67 | [ 68 | 'host' => env('MEMCACHED_HOST', '127.0.0.1'), 69 | 'port' => env('MEMCACHED_PORT', 11211), 70 | 'weight' => 100, 71 | ], 72 | ], 73 | ], 74 | 75 | 'redis' => [ 76 | 'driver' => 'redis', 77 | 'connection' => 'cache', 78 | ], 79 | 80 | 'dynamodb' => [ 81 | 'driver' => 'dynamodb', 82 | 'key' => env('AWS_ACCESS_KEY_ID'), 83 | 'secret' => env('AWS_SECRET_ACCESS_KEY'), 84 | 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), 85 | 'table' => env('DYNAMODB_CACHE_TABLE', 'cache'), 86 | 'endpoint' => env('DYNAMODB_ENDPOINT'), 87 | ], 88 | 89 | ], 90 | 91 | /* 92 | |-------------------------------------------------------------------------- 93 | | Cache Key Prefix 94 | |-------------------------------------------------------------------------- 95 | | 96 | | When utilizing a RAM based store such as APC or Memcached, there might 97 | | be other applications utilizing the same cache. So, we'll specify a 98 | | value to get prefixed to all our keys so we can avoid collisions. 99 | | 100 | */ 101 | 102 | 'prefix' => env('CACHE_PREFIX', Str::slug(env('APP_NAME', 'laravel'), '_').'_cache'), 103 | 104 | ]; 105 | -------------------------------------------------------------------------------- /config/cors.php: -------------------------------------------------------------------------------- 1 | ['api/*'], 19 | 20 | 'allowed_methods' => ['*'], 21 | 22 | 'allowed_origins' => ['*'], 23 | 24 | 'allowed_origins_patterns' => [], 25 | 26 | 'allowed_headers' => ['*'], 27 | 28 | 'exposed_headers' => [], 29 | 30 | 'max_age' => 0, 31 | 32 | 'supports_credentials' => false, 33 | 34 | ]; 35 | -------------------------------------------------------------------------------- /config/database.php: -------------------------------------------------------------------------------- 1 | env('DB_CONNECTION', 'mysql'), 19 | 20 | /* 21 | |-------------------------------------------------------------------------- 22 | | Database Connections 23 | |-------------------------------------------------------------------------- 24 | | 25 | | Here are each of the database connections setup for your application. 26 | | Of course, examples of configuring each database platform that is 27 | | supported by Laravel is shown below to make development simple. 28 | | 29 | | 30 | | All database work in Laravel is done through the PHP PDO facilities 31 | | so make sure you have the driver for your particular database of 32 | | choice installed on your machine before you begin development. 33 | | 34 | */ 35 | 36 | 'connections' => [ 37 | 38 | 'sqlite' => [ 39 | 'driver' => 'sqlite', 40 | 'url' => env('DATABASE_URL'), 41 | 'database' => env('DB_DATABASE', database_path('database.sqlite')), 42 | 'prefix' => '', 43 | 'foreign_key_constraints' => env('DB_FOREIGN_KEYS', true), 44 | ], 45 | 46 | 'mysql' => [ 47 | 'driver' => 'mysql', 48 | 'url' => env('DATABASE_URL'), 49 | 'host' => env('DB_HOST', '127.0.0.1'), 50 | 'port' => env('DB_PORT', '3306'), 51 | 'database' => env('DB_DATABASE', 'forge'), 52 | 'username' => env('DB_USERNAME', 'forge'), 53 | 'password' => env('DB_PASSWORD', ''), 54 | 'unix_socket' => env('DB_SOCKET', ''), 55 | 'charset' => 'utf8mb4', 56 | 'collation' => 'utf8mb4_unicode_ci', 57 | 'prefix' => '', 58 | 'prefix_indexes' => true, 59 | 'strict' => true, 60 | 'engine' => null, 61 | 'options' => extension_loaded('pdo_mysql') ? array_filter([ 62 | PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'), 63 | ]) : [], 64 | ], 65 | 66 | 'pgsql' => [ 67 | 'driver' => 'pgsql', 68 | 'url' => env('DATABASE_URL'), 69 | 'host' => env('DB_HOST', '127.0.0.1'), 70 | 'port' => env('DB_PORT', '5432'), 71 | 'database' => env('DB_DATABASE', 'forge'), 72 | 'username' => env('DB_USERNAME', 'forge'), 73 | 'password' => env('DB_PASSWORD', ''), 74 | 'charset' => 'utf8', 75 | 'prefix' => '', 76 | 'prefix_indexes' => true, 77 | 'schema' => 'public', 78 | 'sslmode' => 'prefer', 79 | ], 80 | 81 | 'sqlsrv' => [ 82 | 'driver' => 'sqlsrv', 83 | 'url' => env('DATABASE_URL'), 84 | 'host' => env('DB_HOST', 'localhost'), 85 | 'port' => env('DB_PORT', '1433'), 86 | 'database' => env('DB_DATABASE', 'forge'), 87 | 'username' => env('DB_USERNAME', 'forge'), 88 | 'password' => env('DB_PASSWORD', ''), 89 | 'charset' => 'utf8', 90 | 'prefix' => '', 91 | 'prefix_indexes' => true, 92 | ], 93 | 94 | ], 95 | 96 | /* 97 | |-------------------------------------------------------------------------- 98 | | Migration Repository Table 99 | |-------------------------------------------------------------------------- 100 | | 101 | | This table keeps track of all the migrations that have already run for 102 | | your application. Using this information, we can determine which of 103 | | the migrations on disk haven't actually been run in the database. 104 | | 105 | */ 106 | 107 | 'migrations' => 'migrations', 108 | 109 | /* 110 | |-------------------------------------------------------------------------- 111 | | Redis Databases 112 | |-------------------------------------------------------------------------- 113 | | 114 | | Redis is an open source, fast, and advanced key-value store that also 115 | | provides a richer body of commands than a typical key-value system 116 | | such as APC or Memcached. Laravel makes it easy to dig right in. 117 | | 118 | */ 119 | 120 | 'redis' => [ 121 | 122 | 'client' => env('REDIS_CLIENT', 'phpredis'), 123 | 124 | 'options' => [ 125 | 'cluster' => env('REDIS_CLUSTER', 'redis'), 126 | 'prefix' => env('REDIS_PREFIX', Str::slug(env('APP_NAME', 'laravel'), '_').'_database_'), 127 | ], 128 | 129 | 'default' => [ 130 | 'url' => env('REDIS_URL'), 131 | 'host' => env('REDIS_HOST', '127.0.0.1'), 132 | 'password' => env('REDIS_PASSWORD', null), 133 | 'port' => env('REDIS_PORT', '6379'), 134 | 'database' => env('REDIS_DB', '0'), 135 | ], 136 | 137 | 'cache' => [ 138 | 'url' => env('REDIS_URL'), 139 | 'host' => env('REDIS_HOST', '127.0.0.1'), 140 | 'password' => env('REDIS_PASSWORD', null), 141 | 'port' => env('REDIS_PORT', '6379'), 142 | 'database' => env('REDIS_CACHE_DB', '1'), 143 | ], 144 | 145 | ], 146 | 147 | ]; 148 | -------------------------------------------------------------------------------- /config/filesystems.php: -------------------------------------------------------------------------------- 1 | env('FILESYSTEM_DRIVER', 'local'), 17 | 18 | /* 19 | |-------------------------------------------------------------------------- 20 | | Default Cloud Filesystem Disk 21 | |-------------------------------------------------------------------------- 22 | | 23 | | Many applications store files both locally and in the cloud. For this 24 | | reason, you may specify a default "cloud" driver here. This driver 25 | | will be bound as the Cloud disk implementation in the container. 26 | | 27 | */ 28 | 29 | 'cloud' => env('FILESYSTEM_CLOUD', 's3'), 30 | 31 | /* 32 | |-------------------------------------------------------------------------- 33 | | Filesystem Disks 34 | |-------------------------------------------------------------------------- 35 | | 36 | | Here you may configure as many filesystem "disks" as you wish, and you 37 | | may even configure multiple disks of the same driver. Defaults have 38 | | been setup for each driver as an example of the required options. 39 | | 40 | | Supported Drivers: "local", "ftp", "sftp", "s3" 41 | | 42 | */ 43 | 44 | 'disks' => [ 45 | 46 | 'local' => [ 47 | 'driver' => 'local', 48 | 'root' => storage_path('app'), 49 | ], 50 | 51 | 'public' => [ 52 | 'driver' => 'local', 53 | 'root' => storage_path('app/public'), 54 | 'url' => env('APP_URL').'/storage', 55 | 'visibility' => 'public', 56 | ], 57 | 58 | 's3' => [ 59 | 'driver' => 's3', 60 | 'key' => env('AWS_ACCESS_KEY_ID'), 61 | 'secret' => env('AWS_SECRET_ACCESS_KEY'), 62 | 'region' => env('AWS_DEFAULT_REGION'), 63 | 'bucket' => env('AWS_BUCKET'), 64 | 'endpoint' => env('AWS_URL'), 65 | ], 66 | 67 | ], 68 | 69 | /* 70 | |-------------------------------------------------------------------------- 71 | | Symbolic Links 72 | |-------------------------------------------------------------------------- 73 | | 74 | | Here you may configure the symbolic links that will be created when the 75 | | `storage:link` Artisan command is executed. The array keys should be 76 | | the locations of the links and the values should be their targets. 77 | | 78 | */ 79 | 80 | 'links' => [ 81 | public_path('storage') => storage_path('app/public'), 82 | ], 83 | 84 | ]; 85 | -------------------------------------------------------------------------------- /config/hashing.php: -------------------------------------------------------------------------------- 1 | 'bcrypt', 19 | 20 | /* 21 | |-------------------------------------------------------------------------- 22 | | Bcrypt Options 23 | |-------------------------------------------------------------------------- 24 | | 25 | | Here you may specify the configuration options that should be used when 26 | | passwords are hashed using the Bcrypt algorithm. This will allow you 27 | | to control the amount of time it takes to hash the given password. 28 | | 29 | */ 30 | 31 | 'bcrypt' => [ 32 | 'rounds' => env('BCRYPT_ROUNDS', 10), 33 | ], 34 | 35 | /* 36 | |-------------------------------------------------------------------------- 37 | | Argon Options 38 | |-------------------------------------------------------------------------- 39 | | 40 | | Here you may specify the configuration options that should be used when 41 | | passwords are hashed using the Argon algorithm. These will allow you 42 | | to control the amount of time it takes to hash the given password. 43 | | 44 | */ 45 | 46 | 'argon' => [ 47 | 'memory' => 1024, 48 | 'threads' => 2, 49 | 'time' => 2, 50 | ], 51 | 52 | ]; 53 | -------------------------------------------------------------------------------- /config/jwt.php: -------------------------------------------------------------------------------- 1 | 7 | * 8 | * For the full copyright and license information, please view the LICENSE 9 | * file that was distributed with this source code. 10 | */ 11 | 12 | return [ 13 | 14 | /* 15 | |-------------------------------------------------------------------------- 16 | | JWT Authentication Secret 17 | |-------------------------------------------------------------------------- 18 | | 19 | | Don't forget to set this in your .env file, as it will be used to sign 20 | | your tokens. A helper command is provided for this: 21 | | `php artisan jwt:secret` 22 | | 23 | | Note: This will be used for Symmetric algorithms only (HMAC), 24 | | since RSA and ECDSA use a private/public key combo (See below). 25 | | 26 | */ 27 | 28 | 'secret' => env('JWT_SECRET'), 29 | 30 | /* 31 | |-------------------------------------------------------------------------- 32 | | JWT Authentication Keys 33 | |-------------------------------------------------------------------------- 34 | | 35 | | The algorithm you are using, will determine whether your tokens are 36 | | signed with a random string (defined in `JWT_SECRET`) or using the 37 | | following public & private keys. 38 | | 39 | | Symmetric Algorithms: 40 | | HS256, HS384 & HS512 will use `JWT_SECRET`. 41 | | 42 | | Asymmetric Algorithms: 43 | | RS256, RS384 & RS512 / ES256, ES384 & ES512 will use the keys below. 44 | | 45 | */ 46 | 47 | 'keys' => [ 48 | 49 | /* 50 | |-------------------------------------------------------------------------- 51 | | Public Key 52 | |-------------------------------------------------------------------------- 53 | | 54 | | A path or resource to your public key. 55 | | 56 | | E.g. 'file://path/to/public/key' 57 | | 58 | */ 59 | 60 | 'public' => env('JWT_PUBLIC_KEY'), 61 | 62 | /* 63 | |-------------------------------------------------------------------------- 64 | | Private Key 65 | |-------------------------------------------------------------------------- 66 | | 67 | | A path or resource to your private key. 68 | | 69 | | E.g. 'file://path/to/private/key' 70 | | 71 | */ 72 | 73 | 'private' => env('JWT_PRIVATE_KEY'), 74 | 75 | /* 76 | |-------------------------------------------------------------------------- 77 | | Passphrase 78 | |-------------------------------------------------------------------------- 79 | | 80 | | The passphrase for your private key. Can be null if none set. 81 | | 82 | */ 83 | 84 | 'passphrase' => env('JWT_PASSPHRASE'), 85 | 86 | ], 87 | 88 | /* 89 | |-------------------------------------------------------------------------- 90 | | JWT time to live 91 | |-------------------------------------------------------------------------- 92 | | 93 | | Specify the length of time (in minutes) that the token will be valid for. 94 | | Defaults to 1 hour. 95 | | 96 | | You can also set this to null, to yield a never expiring token. 97 | | Some people may want this behaviour for e.g. a mobile app. 98 | | This is not particularly recommended, so make sure you have appropriate 99 | | systems in place to revoke the token if necessary. 100 | | Notice: If you set this to null you should remove 'exp' element from 'required_claims' list. 101 | | 102 | */ 103 | 104 | 'ttl' => env('JWT_TTL', 60), 105 | 106 | /* 107 | |-------------------------------------------------------------------------- 108 | | Refresh time to live 109 | |-------------------------------------------------------------------------- 110 | | 111 | | Specify the length of time (in minutes) that the token can be refreshed 112 | | within. I.E. The user can refresh their token within a 2 week window of 113 | | the original token being created until they must re-authenticate. 114 | | Defaults to 2 weeks. 115 | | 116 | | You can also set this to null, to yield an infinite refresh time. 117 | | Some may want this instead of never expiring tokens for e.g. a mobile app. 118 | | This is not particularly recommended, so make sure you have appropriate 119 | | systems in place to revoke the token if necessary. 120 | | 121 | */ 122 | 123 | 'refresh_ttl' => env('JWT_REFRESH_TTL', 20160), 124 | 125 | /* 126 | |-------------------------------------------------------------------------- 127 | | JWT hashing algorithm 128 | |-------------------------------------------------------------------------- 129 | | 130 | | Specify the hashing algorithm that will be used to sign the token. 131 | | 132 | | See here: https://github.com/namshi/jose/tree/master/src/Namshi/JOSE/Signer/OpenSSL 133 | | for possible values. 134 | | 135 | */ 136 | 137 | 'algo' => env('JWT_ALGO', 'HS256'), 138 | 139 | /* 140 | |-------------------------------------------------------------------------- 141 | | Required Claims 142 | |-------------------------------------------------------------------------- 143 | | 144 | | Specify the required claims that must exist in any token. 145 | | A TokenInvalidException will be thrown if any of these claims are not 146 | | present in the payload. 147 | | 148 | */ 149 | 150 | 'required_claims' => [ 151 | 'iss', 152 | 'iat', 153 | 'exp', 154 | 'nbf', 155 | 'sub', 156 | 'jti', 157 | ], 158 | 159 | /* 160 | |-------------------------------------------------------------------------- 161 | | Persistent Claims 162 | |-------------------------------------------------------------------------- 163 | | 164 | | Specify the claim keys to be persisted when refreshing a token. 165 | | `sub` and `iat` will automatically be persisted, in 166 | | addition to the these claims. 167 | | 168 | | Note: If a claim does not exist then it will be ignored. 169 | | 170 | */ 171 | 172 | 'persistent_claims' => [ 173 | // 'foo', 174 | // 'bar', 175 | ], 176 | 177 | /* 178 | |-------------------------------------------------------------------------- 179 | | Lock Subject 180 | |-------------------------------------------------------------------------- 181 | | 182 | | This will determine whether a `prv` claim is automatically added to 183 | | the token. The purpose of this is to ensure that if you have multiple 184 | | authentication models e.g. `App\User` & `App\OtherPerson`, then we 185 | | should prevent one authentication request from impersonating another, 186 | | if 2 tokens happen to have the same id across the 2 different models. 187 | | 188 | | Under specific circumstances, you may want to disable this behaviour 189 | | e.g. if you only have one authentication model, then you would save 190 | | a little on token size. 191 | | 192 | */ 193 | 194 | 'lock_subject' => true, 195 | 196 | /* 197 | |-------------------------------------------------------------------------- 198 | | Leeway 199 | |-------------------------------------------------------------------------- 200 | | 201 | | This property gives the jwt timestamp claims some "leeway". 202 | | Meaning that if you have any unavoidable slight clock skew on 203 | | any of your servers then this will afford you some level of cushioning. 204 | | 205 | | This applies to the claims `iat`, `nbf` and `exp`. 206 | | 207 | | Specify in seconds - only if you know you need it. 208 | | 209 | */ 210 | 211 | 'leeway' => env('JWT_LEEWAY', 0), 212 | 213 | /* 214 | |-------------------------------------------------------------------------- 215 | | Blacklist Enabled 216 | |-------------------------------------------------------------------------- 217 | | 218 | | In order to invalidate tokens, you must have the blacklist enabled. 219 | | If you do not want or need this functionality, then set this to false. 220 | | 221 | */ 222 | 223 | 'blacklist_enabled' => env('JWT_BLACKLIST_ENABLED', true), 224 | 225 | /* 226 | | ------------------------------------------------------------------------- 227 | | Blacklist Grace Period 228 | | ------------------------------------------------------------------------- 229 | | 230 | | When multiple concurrent requests are made with the same JWT, 231 | | it is possible that some of them fail, due to token regeneration 232 | | on every request. 233 | | 234 | | Set grace period in seconds to prevent parallel request failure. 235 | | 236 | */ 237 | 238 | 'blacklist_grace_period' => env('JWT_BLACKLIST_GRACE_PERIOD', 0), 239 | 240 | /* 241 | |-------------------------------------------------------------------------- 242 | | Cookies encryption 243 | |-------------------------------------------------------------------------- 244 | | 245 | | By default Laravel encrypt cookies for security reason. 246 | | If you decide to not decrypt cookies, you will have to configure Laravel 247 | | to not encrypt your cookie token by adding its name into the $except 248 | | array available in the middleware "EncryptCookies" provided by Laravel. 249 | | see https://laravel.com/docs/master/responses#cookies-and-encryption 250 | | for details. 251 | | 252 | | Set it to true if you want to decrypt cookies. 253 | | 254 | */ 255 | 256 | 'decrypt_cookies' => false, 257 | 258 | /* 259 | |-------------------------------------------------------------------------- 260 | | Providers 261 | |-------------------------------------------------------------------------- 262 | | 263 | | Specify the various providers used throughout the package. 264 | | 265 | */ 266 | 267 | 'providers' => [ 268 | 269 | /* 270 | |-------------------------------------------------------------------------- 271 | | JWT Provider 272 | |-------------------------------------------------------------------------- 273 | | 274 | | Specify the provider that is used to create and decode the tokens. 275 | | 276 | */ 277 | 278 | 'jwt' => Tymon\JWTAuth\Providers\JWT\Lcobucci::class, 279 | 280 | /* 281 | |-------------------------------------------------------------------------- 282 | | Authentication Provider 283 | |-------------------------------------------------------------------------- 284 | | 285 | | Specify the provider that is used to authenticate users. 286 | | 287 | */ 288 | 289 | 'auth' => Tymon\JWTAuth\Providers\Auth\Illuminate::class, 290 | 291 | /* 292 | |-------------------------------------------------------------------------- 293 | | Storage Provider 294 | |-------------------------------------------------------------------------- 295 | | 296 | | Specify the provider that is used to store tokens in the blacklist. 297 | | 298 | */ 299 | 300 | 'storage' => Tymon\JWTAuth\Providers\Storage\Illuminate::class, 301 | 302 | ], 303 | 304 | ]; 305 | -------------------------------------------------------------------------------- /config/logging.php: -------------------------------------------------------------------------------- 1 | env('LOG_CHANNEL', 'stack'), 21 | 22 | /* 23 | |-------------------------------------------------------------------------- 24 | | Log Channels 25 | |-------------------------------------------------------------------------- 26 | | 27 | | Here you may configure the log channels for your application. Out of 28 | | the box, Laravel uses the Monolog PHP logging library. This gives 29 | | you a variety of powerful log handlers / formatters to utilize. 30 | | 31 | | Available Drivers: "single", "daily", "slack", "syslog", 32 | | "errorlog", "monolog", 33 | | "custom", "stack" 34 | | 35 | */ 36 | 37 | 'channels' => [ 38 | 'stack' => [ 39 | 'driver' => 'stack', 40 | 'channels' => ['single'], 41 | 'ignore_exceptions' => false, 42 | ], 43 | 44 | 'single' => [ 45 | 'driver' => 'single', 46 | 'path' => storage_path('logs/laravel.log'), 47 | 'level' => 'debug', 48 | ], 49 | 50 | 'daily' => [ 51 | 'driver' => 'daily', 52 | 'path' => storage_path('logs/laravel.log'), 53 | 'level' => 'debug', 54 | 'days' => 14, 55 | ], 56 | 57 | 'slack' => [ 58 | 'driver' => 'slack', 59 | 'url' => env('LOG_SLACK_WEBHOOK_URL'), 60 | 'username' => 'Laravel Log', 61 | 'emoji' => ':boom:', 62 | 'level' => 'critical', 63 | ], 64 | 65 | 'papertrail' => [ 66 | 'driver' => 'monolog', 67 | 'level' => 'debug', 68 | 'handler' => SyslogUdpHandler::class, 69 | 'handler_with' => [ 70 | 'host' => env('PAPERTRAIL_URL'), 71 | 'port' => env('PAPERTRAIL_PORT'), 72 | ], 73 | ], 74 | 75 | 'stderr' => [ 76 | 'driver' => 'monolog', 77 | 'handler' => StreamHandler::class, 78 | 'formatter' => env('LOG_STDERR_FORMATTER'), 79 | 'with' => [ 80 | 'stream' => 'php://stderr', 81 | ], 82 | ], 83 | 84 | 'syslog' => [ 85 | 'driver' => 'syslog', 86 | 'level' => 'debug', 87 | ], 88 | 89 | 'errorlog' => [ 90 | 'driver' => 'errorlog', 91 | 'level' => 'debug', 92 | ], 93 | 94 | 'null' => [ 95 | 'driver' => 'monolog', 96 | 'handler' => NullHandler::class, 97 | ], 98 | 99 | 'emergency' => [ 100 | 'path' => storage_path('logs/laravel.log'), 101 | ], 102 | ], 103 | 104 | ]; 105 | -------------------------------------------------------------------------------- /config/mail.php: -------------------------------------------------------------------------------- 1 | env('MAIL_MAILER', 'smtp'), 17 | 18 | /* 19 | |-------------------------------------------------------------------------- 20 | | Mailer Configurations 21 | |-------------------------------------------------------------------------- 22 | | 23 | | Here you may configure all of the mailers used by your application plus 24 | | their respective settings. Several examples have been configured for 25 | | you and you are free to add your own as your application requires. 26 | | 27 | | Laravel supports a variety of mail "transport" drivers to be used while 28 | | sending an e-mail. You will specify which one you are using for your 29 | | mailers below. You are free to add additional mailers as required. 30 | | 31 | | Supported: "smtp", "sendmail", "mailgun", "ses", 32 | | "postmark", "log", "array" 33 | | 34 | */ 35 | 36 | 'mailers' => [ 37 | 'smtp' => [ 38 | 'transport' => 'smtp', 39 | 'host' => env('MAIL_HOST', 'smtp.mailgun.org'), 40 | 'port' => env('MAIL_PORT', 587), 41 | 'encryption' => env('MAIL_ENCRYPTION', 'tls'), 42 | 'username' => env('MAIL_USERNAME'), 43 | 'password' => env('MAIL_PASSWORD'), 44 | 'timeout' => null, 45 | ], 46 | 47 | 'ses' => [ 48 | 'transport' => 'ses', 49 | ], 50 | 51 | 'mailgun' => [ 52 | 'transport' => 'mailgun', 53 | ], 54 | 55 | 'postmark' => [ 56 | 'transport' => 'postmark', 57 | ], 58 | 59 | 'sendmail' => [ 60 | 'transport' => 'sendmail', 61 | 'path' => '/usr/sbin/sendmail -bs', 62 | ], 63 | 64 | 'log' => [ 65 | 'transport' => 'log', 66 | 'channel' => env('MAIL_LOG_CHANNEL'), 67 | ], 68 | 69 | 'array' => [ 70 | 'transport' => 'array', 71 | ], 72 | ], 73 | 74 | /* 75 | |-------------------------------------------------------------------------- 76 | | Global "From" Address 77 | |-------------------------------------------------------------------------- 78 | | 79 | | You may wish for all e-mails sent by your application to be sent from 80 | | the same address. Here, you may specify a name and address that is 81 | | used globally for all e-mails that are sent by your application. 82 | | 83 | */ 84 | 85 | 'from' => [ 86 | 'address' => env('MAIL_FROM_ADDRESS', 'hello@example.com'), 87 | 'name' => env('MAIL_FROM_NAME', 'Example'), 88 | ], 89 | 90 | /* 91 | |-------------------------------------------------------------------------- 92 | | Markdown Mail Settings 93 | |-------------------------------------------------------------------------- 94 | | 95 | | If you are using Markdown based email rendering, you may configure your 96 | | theme and component paths here, allowing you to customize the design 97 | | of the emails. Or, you may simply stick with the Laravel defaults! 98 | | 99 | */ 100 | 101 | 'markdown' => [ 102 | 'theme' => 'default', 103 | 104 | 'paths' => [ 105 | resource_path('views/vendor/mail'), 106 | ], 107 | ], 108 | 109 | ]; 110 | -------------------------------------------------------------------------------- /config/queue.php: -------------------------------------------------------------------------------- 1 | env('QUEUE_CONNECTION', 'sync'), 17 | 18 | /* 19 | |-------------------------------------------------------------------------- 20 | | Queue Connections 21 | |-------------------------------------------------------------------------- 22 | | 23 | | Here you may configure the connection information for each server that 24 | | is used by your application. A default configuration has been added 25 | | for each back-end shipped with Laravel. You are free to add more. 26 | | 27 | | Drivers: "sync", "database", "beanstalkd", "sqs", "redis", "null" 28 | | 29 | */ 30 | 31 | 'connections' => [ 32 | 33 | 'sync' => [ 34 | 'driver' => 'sync', 35 | ], 36 | 37 | 'database' => [ 38 | 'driver' => 'database', 39 | 'table' => 'jobs', 40 | 'queue' => 'default', 41 | 'retry_after' => 90, 42 | ], 43 | 44 | 'beanstalkd' => [ 45 | 'driver' => 'beanstalkd', 46 | 'host' => 'localhost', 47 | 'queue' => 'default', 48 | 'retry_after' => 90, 49 | 'block_for' => 0, 50 | ], 51 | 52 | 'sqs' => [ 53 | 'driver' => 'sqs', 54 | 'key' => env('AWS_ACCESS_KEY_ID'), 55 | 'secret' => env('AWS_SECRET_ACCESS_KEY'), 56 | 'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'), 57 | 'queue' => env('SQS_QUEUE', 'your-queue-name'), 58 | 'suffix' => env('SQS_SUFFIX'), 59 | 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), 60 | 'token' => env('AWS_SESSION_TOKEN'), 61 | ], 62 | 63 | 'redis' => [ 64 | 'driver' => 'redis', 65 | 'connection' => 'default', 66 | 'queue' => env('REDIS_QUEUE', 'default'), 67 | 'retry_after' => 90, 68 | 'block_for' => null, 69 | ], 70 | 71 | ], 72 | 73 | /* 74 | |-------------------------------------------------------------------------- 75 | | Failed Queue Jobs 76 | |-------------------------------------------------------------------------- 77 | | 78 | | These options configure the behavior of failed queue job logging so you 79 | | can control which database and table are used to store the jobs that 80 | | have failed. You may change them to any database / table you wish. 81 | | 82 | */ 83 | 84 | 'failed' => [ 85 | 'driver' => env('QUEUE_FAILED_DRIVER', 'database'), 86 | 'database' => env('DB_CONNECTION', 'mysql'), 87 | 'table' => 'failed_jobs', 88 | ], 89 | 90 | ]; 91 | -------------------------------------------------------------------------------- /config/response_builder.php: -------------------------------------------------------------------------------- 1 | 100, 13 | 'max_code' => 1024, 14 | 15 | /* 16 | |----------------------------------------------------------------------------------------------------------- 17 | | Error code to message mapping 18 | |----------------------------------------------------------------------------------------------------------- 19 | | 20 | */ 21 | 'map' => [ 22 | ApiCode::SOMETHING_WENT_WRONG => 'api.something_went_wrong', 23 | ApiCode::INVALID_CREDENTIALS => 'api.invalid_credentials', 24 | ApiCode::VALIDATION_ERROR => 'api.validation_error', 25 | ApiCode::INVALID_EMAIL_VERIFICATION_URL => 'api.invalid_email_verification_url', 26 | ApiCode::EMAIL_ALREADY_VERIFIED => 'api.email_already_verified', 27 | ApiCode::INVALID_RESET_PASSWORD_TOKEN => 'api.invalid_reset_password_token', 28 | ], 29 | 30 | ]; 31 | -------------------------------------------------------------------------------- /config/services.php: -------------------------------------------------------------------------------- 1 | [ 18 | 'domain' => env('MAILGUN_DOMAIN'), 19 | 'secret' => env('MAILGUN_SECRET'), 20 | 'endpoint' => env('MAILGUN_ENDPOINT', 'api.mailgun.net'), 21 | ], 22 | 23 | 'postmark' => [ 24 | 'token' => env('POSTMARK_TOKEN'), 25 | ], 26 | 27 | 'ses' => [ 28 | 'key' => env('AWS_ACCESS_KEY_ID'), 29 | 'secret' => env('AWS_SECRET_ACCESS_KEY'), 30 | 'region' => env('AWS_DEFAULT_REGION', 'us-east-1'), 31 | ], 32 | 33 | ]; 34 | -------------------------------------------------------------------------------- /config/session.php: -------------------------------------------------------------------------------- 1 | env('SESSION_DRIVER', 'file'), 22 | 23 | /* 24 | |-------------------------------------------------------------------------- 25 | | Session Lifetime 26 | |-------------------------------------------------------------------------- 27 | | 28 | | Here you may specify the number of minutes that you wish the session 29 | | to be allowed to remain idle before it expires. If you want them 30 | | to immediately expire on the browser closing, set that option. 31 | | 32 | */ 33 | 34 | 'lifetime' => env('SESSION_LIFETIME', 120), 35 | 36 | 'expire_on_close' => false, 37 | 38 | /* 39 | |-------------------------------------------------------------------------- 40 | | Session Encryption 41 | |-------------------------------------------------------------------------- 42 | | 43 | | This option allows you to easily specify that all of your session data 44 | | should be encrypted before it is stored. All encryption will be run 45 | | automatically by Laravel and you can use the Session like normal. 46 | | 47 | */ 48 | 49 | 'encrypt' => false, 50 | 51 | /* 52 | |-------------------------------------------------------------------------- 53 | | Session File Location 54 | |-------------------------------------------------------------------------- 55 | | 56 | | When using the native session driver, we need a location where session 57 | | files may be stored. A default has been set for you but a different 58 | | location may be specified. This is only needed for file sessions. 59 | | 60 | */ 61 | 62 | 'files' => storage_path('framework/sessions'), 63 | 64 | /* 65 | |-------------------------------------------------------------------------- 66 | | Session Database Connection 67 | |-------------------------------------------------------------------------- 68 | | 69 | | When using the "database" or "redis" session drivers, you may specify a 70 | | connection that should be used to manage these sessions. This should 71 | | correspond to a connection in your database configuration options. 72 | | 73 | */ 74 | 75 | 'connection' => env('SESSION_CONNECTION', null), 76 | 77 | /* 78 | |-------------------------------------------------------------------------- 79 | | Session Database Table 80 | |-------------------------------------------------------------------------- 81 | | 82 | | When using the "database" session driver, you may specify the table we 83 | | should use to manage the sessions. Of course, a sensible default is 84 | | provided for you; however, you are free to change this as needed. 85 | | 86 | */ 87 | 88 | 'table' => 'sessions', 89 | 90 | /* 91 | |-------------------------------------------------------------------------- 92 | | Session Cache Store 93 | |-------------------------------------------------------------------------- 94 | | 95 | | When using the "apc", "memcached", or "dynamodb" session drivers you may 96 | | list a cache store that should be used for these sessions. This value 97 | | must match with one of the application's configured cache "stores". 98 | | 99 | */ 100 | 101 | 'store' => env('SESSION_STORE', null), 102 | 103 | /* 104 | |-------------------------------------------------------------------------- 105 | | Session Sweeping Lottery 106 | |-------------------------------------------------------------------------- 107 | | 108 | | Some session drivers must manually sweep their storage location to get 109 | | rid of old sessions from storage. Here are the chances that it will 110 | | happen on a given request. By default, the odds are 2 out of 100. 111 | | 112 | */ 113 | 114 | 'lottery' => [2, 100], 115 | 116 | /* 117 | |-------------------------------------------------------------------------- 118 | | Session Cookie Name 119 | |-------------------------------------------------------------------------- 120 | | 121 | | Here you may change the name of the cookie used to identify a session 122 | | instance by ID. The name specified here will get used every time a 123 | | new session cookie is created by the framework for every driver. 124 | | 125 | */ 126 | 127 | 'cookie' => env( 128 | 'SESSION_COOKIE', 129 | Str::slug(env('APP_NAME', 'laravel'), '_').'_session' 130 | ), 131 | 132 | /* 133 | |-------------------------------------------------------------------------- 134 | | Session Cookie Path 135 | |-------------------------------------------------------------------------- 136 | | 137 | | The session cookie path determines the path for which the cookie will 138 | | be regarded as available. Typically, this will be the root path of 139 | | your application but you are free to change this when necessary. 140 | | 141 | */ 142 | 143 | 'path' => '/', 144 | 145 | /* 146 | |-------------------------------------------------------------------------- 147 | | Session Cookie Domain 148 | |-------------------------------------------------------------------------- 149 | | 150 | | Here you may change the domain of the cookie used to identify a session 151 | | in your application. This will determine which domains the cookie is 152 | | available to in your application. A sensible default has been set. 153 | | 154 | */ 155 | 156 | 'domain' => env('SESSION_DOMAIN', null), 157 | 158 | /* 159 | |-------------------------------------------------------------------------- 160 | | HTTPS Only Cookies 161 | |-------------------------------------------------------------------------- 162 | | 163 | | By setting this option to true, session cookies will only be sent back 164 | | to the server if the browser has a HTTPS connection. This will keep 165 | | the cookie from being sent to you if it can not be done securely. 166 | | 167 | */ 168 | 169 | 'secure' => env('SESSION_SECURE_COOKIE'), 170 | 171 | /* 172 | |-------------------------------------------------------------------------- 173 | | HTTP Access Only 174 | |-------------------------------------------------------------------------- 175 | | 176 | | Setting this value to true will prevent JavaScript from accessing the 177 | | value of the cookie and the cookie will only be accessible through 178 | | the HTTP protocol. You are free to modify this option if needed. 179 | | 180 | */ 181 | 182 | 'http_only' => true, 183 | 184 | /* 185 | |-------------------------------------------------------------------------- 186 | | Same-Site Cookies 187 | |-------------------------------------------------------------------------- 188 | | 189 | | This option determines how your cookies behave when cross-site requests 190 | | take place, and can be used to mitigate CSRF attacks. By default, we 191 | | do not enable this as other CSRF protection services are in place. 192 | | 193 | | Supported: "lax", "strict", "none", null 194 | | 195 | */ 196 | 197 | 'same_site' => 'lax', 198 | 199 | ]; 200 | -------------------------------------------------------------------------------- /config/telescope.php: -------------------------------------------------------------------------------- 1 | env('TELESCOPE_DOMAIN', null), 20 | 21 | /* 22 | |-------------------------------------------------------------------------- 23 | | Telescope Path 24 | |-------------------------------------------------------------------------- 25 | | 26 | | This is the URI path where Telescope will be accessible from. Feel free 27 | | to change this path to anything you like. Note that the URI will not 28 | | affect the paths of its internal API that aren't exposed to users. 29 | | 30 | */ 31 | 32 | 'path' => env('TELESCOPE_PATH', 'telescope'), 33 | 34 | /* 35 | |-------------------------------------------------------------------------- 36 | | Telescope Storage Driver 37 | |-------------------------------------------------------------------------- 38 | | 39 | | This configuration options determines the storage driver that will 40 | | be used to store Telescope's data. In addition, you may set any 41 | | custom options as needed by the particular driver you choose. 42 | | 43 | */ 44 | 45 | 'driver' => env('TELESCOPE_DRIVER', 'database'), 46 | 47 | 'storage' => [ 48 | 'database' => [ 49 | 'connection' => env('DB_CONNECTION', 'mysql'), 50 | 'chunk' => 1000, 51 | ], 52 | ], 53 | 54 | /* 55 | |-------------------------------------------------------------------------- 56 | | Telescope Master Switch 57 | |-------------------------------------------------------------------------- 58 | | 59 | | This option may be used to disable all Telescope watchers regardless 60 | | of their individual configuration, which simply provides a single 61 | | and convenient way to enable or disable Telescope data storage. 62 | | 63 | */ 64 | 65 | 'enabled' => env('TELESCOPE_ENABLED', true), 66 | 67 | /* 68 | |-------------------------------------------------------------------------- 69 | | Telescope Route Middleware 70 | |-------------------------------------------------------------------------- 71 | | 72 | | These middleware will be assigned to every Telescope route, giving you 73 | | the chance to add your own middleware to this list or change any of 74 | | the existing middleware. Or, you can simply stick with this list. 75 | | 76 | */ 77 | 78 | 'middleware' => [ 79 | 'web', 80 | Authorize::class, 81 | ], 82 | 83 | /* 84 | |-------------------------------------------------------------------------- 85 | | Ignored Paths & Commands 86 | |-------------------------------------------------------------------------- 87 | | 88 | | The following array lists the URI paths and Artisan commands that will 89 | | not be watched by Telescope. In addition to this list, some Laravel 90 | | commands, like migrations and queue commands, are always ignored. 91 | | 92 | */ 93 | 94 | 'ignore_paths' => [ 95 | 'nova-api*', 96 | ], 97 | 98 | 'ignore_commands' => [ 99 | // 100 | ], 101 | 102 | /* 103 | |-------------------------------------------------------------------------- 104 | | Telescope Watchers 105 | |-------------------------------------------------------------------------- 106 | | 107 | | The following array lists the "watchers" that will be registered with 108 | | Telescope. The watchers gather the application's profile data when 109 | | a request or task is executed. Feel free to customize this list. 110 | | 111 | */ 112 | 113 | 'watchers' => [ 114 | Watchers\CacheWatcher::class => env('TELESCOPE_CACHE_WATCHER', true), 115 | 116 | Watchers\CommandWatcher::class => [ 117 | 'enabled' => env('TELESCOPE_COMMAND_WATCHER', true), 118 | 'ignore' => [], 119 | ], 120 | 121 | Watchers\DumpWatcher::class => env('TELESCOPE_DUMP_WATCHER', true), 122 | 123 | Watchers\EventWatcher::class => [ 124 | 'enabled' => env('TELESCOPE_EVENT_WATCHER', true), 125 | 'ignore' => [], 126 | ], 127 | 128 | Watchers\ExceptionWatcher::class => env('TELESCOPE_EXCEPTION_WATCHER', true), 129 | Watchers\JobWatcher::class => env('TELESCOPE_JOB_WATCHER', true), 130 | Watchers\LogWatcher::class => env('TELESCOPE_LOG_WATCHER', true), 131 | Watchers\MailWatcher::class => env('TELESCOPE_MAIL_WATCHER', true), 132 | 133 | Watchers\ModelWatcher::class => [ 134 | 'enabled' => env('TELESCOPE_MODEL_WATCHER', true), 135 | 'events' => ['eloquent.*'], 136 | ], 137 | 138 | Watchers\NotificationWatcher::class => env('TELESCOPE_NOTIFICATION_WATCHER', true), 139 | 140 | Watchers\QueryWatcher::class => [ 141 | 'enabled' => env('TELESCOPE_QUERY_WATCHER', true), 142 | 'ignore_packages' => true, 143 | 'slow' => 100, 144 | ], 145 | 146 | Watchers\RedisWatcher::class => env('TELESCOPE_REDIS_WATCHER', true), 147 | 148 | Watchers\RequestWatcher::class => [ 149 | 'enabled' => env('TELESCOPE_REQUEST_WATCHER', true), 150 | 'size_limit' => env('TELESCOPE_RESPONSE_SIZE_LIMIT', 64), 151 | ], 152 | 153 | Watchers\GateWatcher::class => [ 154 | 'enabled' => env('TELESCOPE_GATE_WATCHER', true), 155 | 'ignore_abilities' => [], 156 | 'ignore_packages' => true, 157 | ], 158 | 159 | Watchers\ScheduleWatcher::class => env('TELESCOPE_SCHEDULE_WATCHER', true), 160 | 161 | Watchers\ViewWatcher::class => env('TELESCOPE_VIEW_WATCHER', true), 162 | ], 163 | ]; 164 | -------------------------------------------------------------------------------- /config/view.php: -------------------------------------------------------------------------------- 1 | [ 17 | resource_path('views'), 18 | ], 19 | 20 | /* 21 | |-------------------------------------------------------------------------- 22 | | Compiled View Path 23 | |-------------------------------------------------------------------------- 24 | | 25 | | This option determines where all the compiled Blade templates will be 26 | | stored for your application. Typically, this is within the storage 27 | | directory. However, as usual, you are free to change this value. 28 | | 29 | */ 30 | 31 | 'compiled' => env( 32 | 'VIEW_COMPILED_PATH', 33 | realpath(storage_path('framework/views')) 34 | ), 35 | 36 | ]; 37 | -------------------------------------------------------------------------------- /database/.gitignore: -------------------------------------------------------------------------------- 1 | *.sqlite 2 | *.sqlite-journal 3 | -------------------------------------------------------------------------------- /database/factories/UserFactory.php: -------------------------------------------------------------------------------- 1 | define(\App\User::class, function (Faker $faker) { 9 | return [ 10 | 'name' => $faker->name, 11 | 'email' => $faker->unique()->safeEmail, 12 | 'email_verified_at' => now(), 13 | 'password' => \Illuminate\Support\Facades\Hash::make($faker->password), 14 | 'remember_token' => \Illuminate\Support\Str::random(8) 15 | ]; 16 | }); 17 | -------------------------------------------------------------------------------- /database/migrations/2014_10_12_000000_create_users_table.php: -------------------------------------------------------------------------------- 1 | id(); 18 | $table->string('name'); 19 | $table->string('email')->unique(); 20 | $table->timestamp('email_verified_at')->nullable(); 21 | $table->string('password'); 22 | $table->rememberToken(); 23 | $table->timestamps(); 24 | }); 25 | } 26 | 27 | /** 28 | * Reverse the migrations. 29 | * 30 | * @return void 31 | */ 32 | public function down() 33 | { 34 | Schema::dropIfExists('users'); 35 | } 36 | } 37 | -------------------------------------------------------------------------------- /database/migrations/2019_08_19_000000_create_failed_jobs_table.php: -------------------------------------------------------------------------------- 1 | id(); 18 | $table->text('connection'); 19 | $table->text('queue'); 20 | $table->longText('payload'); 21 | $table->longText('exception'); 22 | $table->timestamp('failed_at')->useCurrent(); 23 | }); 24 | } 25 | 26 | /** 27 | * Reverse the migrations. 28 | * 29 | * @return void 30 | */ 31 | public function down() 32 | { 33 | Schema::dropIfExists('failed_jobs'); 34 | } 35 | } 36 | -------------------------------------------------------------------------------- /database/seeds/DatabaseSeeder.php: -------------------------------------------------------------------------------- 1 | call(UsersTableSeeder::class); 15 | } 16 | } 17 | -------------------------------------------------------------------------------- /database/seeds/UsersTableSeeder.php: -------------------------------------------------------------------------------- 1 | create(); 15 | } 16 | } 17 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "private": true, 3 | "scripts": { 4 | "dev": "npm run development", 5 | "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js", 6 | "watch": "npm run development -- --watch", 7 | "watch-poll": "npm run watch -- --watch-poll", 8 | "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js", 9 | "prod": "npm run production", 10 | "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js" 11 | }, 12 | "devDependencies": { 13 | "axios": "^0.19", 14 | "cross-env": "^7.0", 15 | "laravel-mix": "^5.0.1", 16 | "lodash": "^4.17.13", 17 | "resolve-url-loader": "^3.1.0", 18 | "sass": "^1.15.2", 19 | "sass-loader": "^8.0.0" 20 | } 21 | } 22 | -------------------------------------------------------------------------------- /phpunit.xml: -------------------------------------------------------------------------------- 1 | 2 | 6 | 7 | 8 | ./tests/Unit 9 | 10 | 11 | ./tests/Feature 12 | 13 | 14 | 15 | 16 | ./app 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /public/.htaccess: -------------------------------------------------------------------------------- 1 | 2 | 3 | Options -MultiViews -Indexes 4 | 5 | 6 | RewriteEngine On 7 | 8 | # Handle Authorization Header 9 | RewriteCond %{HTTP:Authorization} . 10 | RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] 11 | 12 | # Redirect Trailing Slashes If Not A Folder... 13 | RewriteCond %{REQUEST_FILENAME} !-d 14 | RewriteCond %{REQUEST_URI} (.+)/$ 15 | RewriteRule ^ %1 [L,R=301] 16 | 17 | # Send Requests To Front Controller... 18 | RewriteCond %{REQUEST_FILENAME} !-d 19 | RewriteCond %{REQUEST_FILENAME} !-f 20 | RewriteRule ^ index.php [L] 21 | 22 | -------------------------------------------------------------------------------- /public/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/csinghdev/laravel-starter-serverless/5e5e459bfa09d30f83736c5f2db96511e82d83e3/public/favicon.ico -------------------------------------------------------------------------------- /public/index.php: -------------------------------------------------------------------------------- 1 | 8 | */ 9 | 10 | define('LARAVEL_START', microtime(true)); 11 | 12 | /* 13 | |-------------------------------------------------------------------------- 14 | | Register The Auto Loader 15 | |-------------------------------------------------------------------------- 16 | | 17 | | Composer provides a convenient, automatically generated class loader for 18 | | our application. We just need to utilize it! We'll simply require it 19 | | into the script here so that we don't have to worry about manual 20 | | loading any of our classes later on. It feels great to relax. 21 | | 22 | */ 23 | 24 | require __DIR__.'/../vendor/autoload.php'; 25 | 26 | /* 27 | |-------------------------------------------------------------------------- 28 | | Turn On The Lights 29 | |-------------------------------------------------------------------------- 30 | | 31 | | We need to illuminate PHP development, so let us turn on the lights. 32 | | This bootstraps the framework and gets it ready for use, then it 33 | | will load up this application so that we can run it and send 34 | | the responses back to the browser and delight our users. 35 | | 36 | */ 37 | 38 | $app = require_once __DIR__.'/../bootstrap/app.php'; 39 | 40 | /* 41 | |-------------------------------------------------------------------------- 42 | | Run The Application 43 | |-------------------------------------------------------------------------- 44 | | 45 | | Once we have the application, we can handle the incoming request 46 | | through the kernel, and send the associated response back to 47 | | the client's browser allowing them to enjoy the creative 48 | | and wonderful application we have prepared for them. 49 | | 50 | */ 51 | 52 | $kernel = $app->make(Illuminate\Contracts\Http\Kernel::class); 53 | 54 | $response = $kernel->handle( 55 | $request = Illuminate\Http\Request::capture() 56 | ); 57 | 58 | $response->send(); 59 | 60 | $kernel->terminate($request, $response); 61 | -------------------------------------------------------------------------------- /public/robots.txt: -------------------------------------------------------------------------------- 1 | User-agent: * 2 | Disallow: 3 | -------------------------------------------------------------------------------- /public/vendor/telescope/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/csinghdev/laravel-starter-serverless/5e5e459bfa09d30f83736c5f2db96511e82d83e3/public/vendor/telescope/favicon.ico -------------------------------------------------------------------------------- /public/vendor/telescope/mix-manifest.json: -------------------------------------------------------------------------------- 1 | { 2 | "/app.js": "/app.js?id=2cc598321134a0bcfac1", 3 | "/app.css": "/app.css?id=d79fb7e75cd04c97ef92", 4 | "/app-dark.css": "/app-dark.css?id=af37df8013614303ea68" 5 | } 6 | -------------------------------------------------------------------------------- /public/web.config: -------------------------------------------------------------------------------- 1 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /resources/js/app.js: -------------------------------------------------------------------------------- 1 | require('./bootstrap'); 2 | -------------------------------------------------------------------------------- /resources/js/bootstrap.js: -------------------------------------------------------------------------------- 1 | window._ = require('lodash'); 2 | 3 | /** 4 | * We'll load the axios HTTP library which allows us to easily issue requests 5 | * to our Laravel back-end. This library automatically handles sending the 6 | * CSRF token as a header based on the value of the "XSRF" token cookie. 7 | */ 8 | 9 | window.axios = require('axios'); 10 | 11 | window.axios.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest'; 12 | 13 | /** 14 | * Echo exposes an expressive API for subscribing to channels and listening 15 | * for events that are broadcast by Laravel. Echo and event broadcasting 16 | * allows your team to easily build robust real-time web applications. 17 | */ 18 | 19 | // import Echo from 'laravel-echo'; 20 | 21 | // window.Pusher = require('pusher-js'); 22 | 23 | // window.Echo = new Echo({ 24 | // broadcaster: 'pusher', 25 | // key: process.env.MIX_PUSHER_APP_KEY, 26 | // cluster: process.env.MIX_PUSHER_APP_CLUSTER, 27 | // forceTLS: true 28 | // }); 29 | -------------------------------------------------------------------------------- /resources/lang/en/api.php: -------------------------------------------------------------------------------- 1 | 'Ops! Something went wrong.', 17 | 'invalid_credentials' => 'Invalid email or password.', 18 | 'validation_error' => 'Validation Error', 19 | 'invalid_email_verification_url' => 'Invalid url provided.', 20 | 'email_already_verified' => 'You have already verified email.', 21 | 'invalid_reset_password_token' => 'Invalid token provided.' 22 | ]; 23 | -------------------------------------------------------------------------------- /resources/lang/en/auth.php: -------------------------------------------------------------------------------- 1 | 'These credentials do not match our records.', 17 | 'throttle' => 'Too many login attempts. Please try again in :seconds seconds.', 18 | 19 | ]; 20 | -------------------------------------------------------------------------------- /resources/lang/en/pagination.php: -------------------------------------------------------------------------------- 1 | '« Previous', 17 | 'next' => 'Next »', 18 | 19 | ]; 20 | -------------------------------------------------------------------------------- /resources/lang/en/passwords.php: -------------------------------------------------------------------------------- 1 | 'Your password has been reset!', 17 | 'sent' => 'We have emailed your password reset link!', 18 | 'throttled' => 'Please wait before retrying.', 19 | 'token' => 'This password reset token is invalid.', 20 | 'user' => "We can't find a user with that email address.", 21 | 22 | ]; 23 | -------------------------------------------------------------------------------- /resources/lang/en/validation.php: -------------------------------------------------------------------------------- 1 | 'The :attribute must be accepted.', 17 | 'active_url' => 'The :attribute is not a valid URL.', 18 | 'after' => 'The :attribute must be a date after :date.', 19 | 'after_or_equal' => 'The :attribute must be a date after or equal to :date.', 20 | 'alpha' => 'The :attribute may only contain letters.', 21 | 'alpha_dash' => 'The :attribute may only contain letters, numbers, dashes and underscores.', 22 | 'alpha_num' => 'The :attribute may only contain letters and numbers.', 23 | 'array' => 'The :attribute must be an array.', 24 | 'before' => 'The :attribute must be a date before :date.', 25 | 'before_or_equal' => 'The :attribute must be a date before or equal to :date.', 26 | 'between' => [ 27 | 'numeric' => 'The :attribute must be between :min and :max.', 28 | 'file' => 'The :attribute must be between :min and :max kilobytes.', 29 | 'string' => 'The :attribute must be between :min and :max characters.', 30 | 'array' => 'The :attribute must have between :min and :max items.', 31 | ], 32 | 'boolean' => 'The :attribute field must be true or false.', 33 | 'confirmed' => 'The :attribute confirmation does not match.', 34 | 'date' => 'The :attribute is not a valid date.', 35 | 'date_equals' => 'The :attribute must be a date equal to :date.', 36 | 'date_format' => 'The :attribute does not match the format :format.', 37 | 'different' => 'The :attribute and :other must be different.', 38 | 'digits' => 'The :attribute must be :digits digits.', 39 | 'digits_between' => 'The :attribute must be between :min and :max digits.', 40 | 'dimensions' => 'The :attribute has invalid image dimensions.', 41 | 'distinct' => 'The :attribute field has a duplicate value.', 42 | 'email' => 'The :attribute must be a valid email address.', 43 | 'ends_with' => 'The :attribute must end with one of the following: :values.', 44 | 'exists' => 'The selected :attribute is invalid.', 45 | 'file' => 'The :attribute must be a file.', 46 | 'filled' => 'The :attribute field must have a value.', 47 | 'gt' => [ 48 | 'numeric' => 'The :attribute must be greater than :value.', 49 | 'file' => 'The :attribute must be greater than :value kilobytes.', 50 | 'string' => 'The :attribute must be greater than :value characters.', 51 | 'array' => 'The :attribute must have more than :value items.', 52 | ], 53 | 'gte' => [ 54 | 'numeric' => 'The :attribute must be greater than or equal :value.', 55 | 'file' => 'The :attribute must be greater than or equal :value kilobytes.', 56 | 'string' => 'The :attribute must be greater than or equal :value characters.', 57 | 'array' => 'The :attribute must have :value items or more.', 58 | ], 59 | 'image' => 'The :attribute must be an image.', 60 | 'in' => 'The selected :attribute is invalid.', 61 | 'in_array' => 'The :attribute field does not exist in :other.', 62 | 'integer' => 'The :attribute must be an integer.', 63 | 'ip' => 'The :attribute must be a valid IP address.', 64 | 'ipv4' => 'The :attribute must be a valid IPv4 address.', 65 | 'ipv6' => 'The :attribute must be a valid IPv6 address.', 66 | 'json' => 'The :attribute must be a valid JSON string.', 67 | 'lt' => [ 68 | 'numeric' => 'The :attribute must be less than :value.', 69 | 'file' => 'The :attribute must be less than :value kilobytes.', 70 | 'string' => 'The :attribute must be less than :value characters.', 71 | 'array' => 'The :attribute must have less than :value items.', 72 | ], 73 | 'lte' => [ 74 | 'numeric' => 'The :attribute must be less than or equal :value.', 75 | 'file' => 'The :attribute must be less than or equal :value kilobytes.', 76 | 'string' => 'The :attribute must be less than or equal :value characters.', 77 | 'array' => 'The :attribute must not have more than :value items.', 78 | ], 79 | 'max' => [ 80 | 'numeric' => 'The :attribute may not be greater than :max.', 81 | 'file' => 'The :attribute may not be greater than :max kilobytes.', 82 | 'string' => 'The :attribute may not be greater than :max characters.', 83 | 'array' => 'The :attribute may not have more than :max items.', 84 | ], 85 | 'mimes' => 'The :attribute must be a file of type: :values.', 86 | 'mimetypes' => 'The :attribute must be a file of type: :values.', 87 | 'min' => [ 88 | 'numeric' => 'The :attribute must be at least :min.', 89 | 'file' => 'The :attribute must be at least :min kilobytes.', 90 | 'string' => 'The :attribute must be at least :min characters.', 91 | 'array' => 'The :attribute must have at least :min items.', 92 | ], 93 | 'not_in' => 'The selected :attribute is invalid.', 94 | 'not_regex' => 'The :attribute format is invalid.', 95 | 'numeric' => 'The :attribute must be a number.', 96 | 'password' => 'The password is incorrect.', 97 | 'present' => 'The :attribute field must be present.', 98 | 'regex' => 'The :attribute format is invalid.', 99 | 'required' => 'The :attribute field is required.', 100 | 'required_if' => 'The :attribute field is required when :other is :value.', 101 | 'required_unless' => 'The :attribute field is required unless :other is in :values.', 102 | 'required_with' => 'The :attribute field is required when :values is present.', 103 | 'required_with_all' => 'The :attribute field is required when :values are present.', 104 | 'required_without' => 'The :attribute field is required when :values is not present.', 105 | 'required_without_all' => 'The :attribute field is required when none of :values are present.', 106 | 'same' => 'The :attribute and :other must match.', 107 | 'size' => [ 108 | 'numeric' => 'The :attribute must be :size.', 109 | 'file' => 'The :attribute must be :size kilobytes.', 110 | 'string' => 'The :attribute must be :size characters.', 111 | 'array' => 'The :attribute must contain :size items.', 112 | ], 113 | 'starts_with' => 'The :attribute must start with one of the following: :values.', 114 | 'string' => 'The :attribute must be a string.', 115 | 'timezone' => 'The :attribute must be a valid zone.', 116 | 'unique' => 'The :attribute has already been taken.', 117 | 'uploaded' => 'The :attribute failed to upload.', 118 | 'url' => 'The :attribute format is invalid.', 119 | 'uuid' => 'The :attribute must be a valid UUID.', 120 | 121 | /* 122 | |-------------------------------------------------------------------------- 123 | | Custom Validation Language Lines 124 | |-------------------------------------------------------------------------- 125 | | 126 | | Here you may specify custom validation messages for attributes using the 127 | | convention "attribute.rule" to name the lines. This makes it quick to 128 | | specify a specific custom language line for a given attribute rule. 129 | | 130 | */ 131 | 132 | 'custom' => [ 133 | 'attribute-name' => [ 134 | 'rule-name' => 'custom-message', 135 | ], 136 | ], 137 | 138 | /* 139 | |-------------------------------------------------------------------------- 140 | | Custom Validation Attributes 141 | |-------------------------------------------------------------------------- 142 | | 143 | | The following language lines are used to swap our attribute placeholder 144 | | with something more reader friendly such as "E-Mail Address" instead 145 | | of "email". This simply helps us make our message more expressive. 146 | | 147 | */ 148 | 149 | 'attributes' => [], 150 | 151 | ]; 152 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/ar/notifications.php: -------------------------------------------------------------------------------- 1 | 'رسالة استثناء: :message', 5 | 'exception_trace' => 'تتبع الإستثناء: :trace', 6 | 'exception_message_title' => 'رسالة استثناء', 7 | 'exception_trace_title' => 'تتبع الإستثناء', 8 | 9 | 'backup_failed_subject' => 'أخفق النسخ الاحتياطي لل :application_name', 10 | 'backup_failed_body' => 'مهم: حدث خطأ أثناء النسخ الاحتياطي :application_name', 11 | 12 | 'backup_successful_subject' => 'نسخ احتياطي جديد ناجح ل :application_name', 13 | 'backup_successful_subject_title' => 'نجاح النسخ الاحتياطي الجديد!', 14 | 'backup_successful_body' => 'أخبار عظيمة، نسخة احتياطية جديدة ل :application_name تم إنشاؤها بنجاح على القرص المسمى :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'فشل تنظيف النسخ الاحتياطي للتطبيق :application_name .', 17 | 'cleanup_failed_body' => 'حدث خطأ أثناء تنظيف النسخ الاحتياطية ل :application_name', 18 | 19 | 'cleanup_successful_subject' => 'تنظيف النسخ الاحتياطية ل :application_name تمت بنجاح', 20 | 'cleanup_successful_subject_title' => 'تنظيف النسخ الاحتياطية تم بنجاح!', 21 | 'cleanup_successful_body' => 'تنظيف النسخ الاحتياطية ل :application_name على القرص المسمى :disk_name تم بنجاح.', 22 | 23 | 'healthy_backup_found_subject' => 'النسخ الاحتياطية ل :application_name على القرص :disk_name صحية', 24 | 'healthy_backup_found_subject_title' => 'النسخ الاحتياطية ل :application_name صحية', 25 | 'healthy_backup_found_body' => 'تعتبر النسخ الاحتياطية ل :application_name صحية. عمل جيد!', 26 | 27 | 'unhealthy_backup_found_subject' => 'مهم: النسخ الاحتياطية ل :application_name غير صحية', 28 | 'unhealthy_backup_found_subject_title' => 'مهم: النسخ الاحتياطية ل :application_name غير صحية. :problem', 29 | 'unhealthy_backup_found_body' => 'النسخ الاحتياطية ل :application_name على القرص :disk_name غير صحية.', 30 | 'unhealthy_backup_found_not_reachable' => 'لا يمكن الوصول إلى وجهة النسخ الاحتياطي. :error', 31 | 'unhealthy_backup_found_empty' => 'لا توجد نسخ احتياطية لهذا التطبيق على الإطلاق.', 32 | 'unhealthy_backup_found_old' => 'تم إنشاء أحدث النسخ الاحتياطية في :date وتعتبر قديمة جدا.', 33 | 'unhealthy_backup_found_unknown' => 'عذرا، لا يمكن تحديد سبب دقيق.', 34 | 'unhealthy_backup_found_full' => 'النسخ الاحتياطية تستخدم الكثير من التخزين. الاستخدام الحالي هو :disk_usage وهو أعلى من الحد المسموح به من :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/cs/notifications.php: -------------------------------------------------------------------------------- 1 | 'Zpráva výjimky: :message', 5 | 'exception_trace' => 'Stopa výjimky: :trace', 6 | 'exception_message_title' => 'Zpráva výjimky', 7 | 'exception_trace_title' => 'Stopa výjimky', 8 | 9 | 'backup_failed_subject' => 'Záloha :application_name neuspěla', 10 | 'backup_failed_body' => 'Důležité: Při záloze :application_name se vyskytla chyba', 11 | 12 | 'backup_successful_subject' => 'Úspěšná nová záloha :application_name', 13 | 'backup_successful_subject_title' => 'Úspěšná nová záloha!', 14 | 'backup_successful_body' => 'Dobrá zpráva, na disku jménem :disk_name byla úspěšně vytvořena nová záloha :application_name.', 15 | 16 | 'cleanup_failed_subject' => 'Vyčištění záloh :application_name neuspělo.', 17 | 'cleanup_failed_body' => 'Při vyčištění záloh :application_name se vyskytla chyba', 18 | 19 | 'cleanup_successful_subject' => 'Vyčištění záloh :application_name úspěšné', 20 | 'cleanup_successful_subject_title' => 'Vyčištění záloh bylo úspěšné!', 21 | 'cleanup_successful_body' => 'Vyčištění záloh :application_name na disku jménem :disk_name bylo úspěšné.', 22 | 23 | 'healthy_backup_found_subject' => 'Zálohy pro :application_name na disku :disk_name jsou zdravé', 24 | 'healthy_backup_found_subject_title' => 'Zálohy pro :application_name jsou zdravé', 25 | 'healthy_backup_found_body' => 'Zálohy pro :application_name jsou považovány za zdravé. Dobrá práce!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Důležité: Zálohy pro :application_name jsou nezdravé', 28 | 'unhealthy_backup_found_subject_title' => 'Důležité: Zálohy pro :application_name jsou nezdravé. :problem', 29 | 'unhealthy_backup_found_body' => 'Zálohy pro :application_name na disku :disk_name Jsou nezdravé.', 30 | 'unhealthy_backup_found_not_reachable' => 'Nelze se dostat k cíli zálohy. :error', 31 | 'unhealthy_backup_found_empty' => 'Tato aplikace nemá vůbec žádné zálohy.', 32 | 'unhealthy_backup_found_old' => 'Poslední záloha vytvořená dne :date je považována za příliš starou.', 33 | 'unhealthy_backup_found_unknown' => 'Omlouváme se, nemůžeme určit přesný důvod.', 34 | 'unhealthy_backup_found_full' => 'Zálohy zabírají příliš mnoho místa na disku. Aktuální využití disku je :disk_usage, což je vyšší než povolený limit :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/da/notifications.php: -------------------------------------------------------------------------------- 1 | 'Fejlbesked: :message', 5 | 'exception_trace' => 'Fejl trace: :trace', 6 | 'exception_message_title' => 'Fejlbesked', 7 | 'exception_trace_title' => 'Fejl trace', 8 | 9 | 'backup_failed_subject' => 'Backup af :application_name fejlede', 10 | 'backup_failed_body' => 'Vigtigt: Der skete en fejl under backup af :application_name', 11 | 12 | 'backup_successful_subject' => 'Ny backup af :application_name oprettet', 13 | 'backup_successful_subject_title' => 'Ny backup!', 14 | 'backup_successful_body' => 'Gode nyheder - der blev oprettet en ny backup af :application_name på disken :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Oprydning af backups for :application_name fejlede.', 17 | 'cleanup_failed_body' => 'Der skete en fejl under oprydning af backups for :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Oprydning af backups for :application_name gennemført', 20 | 'cleanup_successful_subject_title' => 'Backup oprydning gennemført!', 21 | 'cleanup_successful_body' => 'Oprydningen af backups for :application_name på disken :disk_name er gennemført.', 22 | 23 | 'healthy_backup_found_subject' => 'Alle backups for :application_name på disken :disk_name er OK', 24 | 'healthy_backup_found_subject_title' => 'Alle backups for :application_name er OK', 25 | 'healthy_backup_found_body' => 'Alle backups for :application_name er ok. Godt gået!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Vigtigt: Backups for :application_name fejlbehæftede', 28 | 'unhealthy_backup_found_subject_title' => 'Vigtigt: Backups for :application_name er fejlbehæftede. :problem', 29 | 'unhealthy_backup_found_body' => 'Backups for :application_name på disken :disk_name er fejlbehæftede.', 30 | 'unhealthy_backup_found_not_reachable' => 'Backup destinationen kunne ikke findes. :error', 31 | 'unhealthy_backup_found_empty' => 'Denne applikation har ingen backups overhovedet.', 32 | 'unhealthy_backup_found_old' => 'Den seneste backup fra :date er for gammel.', 33 | 'unhealthy_backup_found_unknown' => 'Beklager, en præcis årsag kunne ikke findes.', 34 | 'unhealthy_backup_found_full' => 'Backups bruger for meget plads. Nuværende disk forbrug er :disk_usage, hvilket er mere end den tilladte grænse på :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/de/notifications.php: -------------------------------------------------------------------------------- 1 | 'Fehlermeldung: :message', 5 | 'exception_trace' => 'Fehlerverfolgung: :trace', 6 | 'exception_message_title' => 'Fehlermeldung', 7 | 'exception_trace_title' => 'Fehlerverfolgung', 8 | 9 | 'backup_failed_subject' => 'Backup von :application_name konnte nicht erstellt werden', 10 | 'backup_failed_body' => 'Wichtig: Beim Backup von :application_name ist ein Fehler aufgetreten', 11 | 12 | 'backup_successful_subject' => 'Erfolgreiches neues Backup von :application_name', 13 | 'backup_successful_subject_title' => 'Erfolgreiches neues Backup!', 14 | 'backup_successful_body' => 'Gute Nachrichten, ein neues Backup von :application_name wurde erfolgreich erstellt und in :disk_name gepeichert.', 15 | 16 | 'cleanup_failed_subject' => 'Aufräumen der Backups von :application_name schlug fehl.', 17 | 'cleanup_failed_body' => 'Beim aufräumen der Backups von :application_name ist ein Fehler aufgetreten', 18 | 19 | 'cleanup_successful_subject' => 'Aufräumen der Backups von :application_name backups erfolgreich', 20 | 'cleanup_successful_subject_title' => 'Aufräumen der Backups erfolgreich!', 21 | 'cleanup_successful_body' => 'Aufräumen der Backups von :application_name in :disk_name war erfolgreich.', 22 | 23 | 'healthy_backup_found_subject' => 'Die Backups von :application_name in :disk_name sind gesund', 24 | 'healthy_backup_found_subject_title' => 'Die Backups von :application_name sind Gesund', 25 | 'healthy_backup_found_body' => 'Die Backups von :application_name wurden als gesund eingestuft. Gute Arbeit!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Wichtig: Die Backups für :application_name sind nicht gesund', 28 | 'unhealthy_backup_found_subject_title' => 'Wichtig: Die Backups für :application_name sind ungesund. :problem', 29 | 'unhealthy_backup_found_body' => 'Die Backups für :application_name in :disk_name sind ungesund.', 30 | 'unhealthy_backup_found_not_reachable' => 'Das Backup Ziel konnte nicht erreicht werden. :error', 31 | 'unhealthy_backup_found_empty' => 'Es gibt für die Anwendung noch gar keine Backups.', 32 | 'unhealthy_backup_found_old' => 'Das letzte Backup am :date ist zu lange her.', 33 | 'unhealthy_backup_found_unknown' => 'Sorry, ein genauer Grund konnte nicht gefunden werden.', 34 | 'unhealthy_backup_found_full' => 'Die Backups verbrauchen zu viel Platz. Aktuell wird :disk_usage belegt, dass ist höher als das erlaubte Limit von :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/en/notifications.php: -------------------------------------------------------------------------------- 1 | 'Exception message: :message', 5 | 'exception_trace' => 'Exception trace: :trace', 6 | 'exception_message_title' => 'Exception message', 7 | 'exception_trace_title' => 'Exception trace', 8 | 9 | 'backup_failed_subject' => 'Failed backup of :application_name', 10 | 'backup_failed_body' => 'Important: An error occurred while backing up :application_name', 11 | 12 | 'backup_successful_subject' => 'Successful new backup of :application_name', 13 | 'backup_successful_subject_title' => 'Successful new backup!', 14 | 'backup_successful_body' => 'Great news, a new backup of :application_name was successfully created on the disk named :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Cleaning up the backups of :application_name failed.', 17 | 'cleanup_failed_body' => 'An error occurred while cleaning up the backups of :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Clean up of :application_name backups successful', 20 | 'cleanup_successful_subject_title' => 'Clean up of backups successful!', 21 | 'cleanup_successful_body' => 'The clean up of the :application_name backups on the disk named :disk_name was successful.', 22 | 23 | 'healthy_backup_found_subject' => 'The backups for :application_name on disk :disk_name are healthy', 24 | 'healthy_backup_found_subject_title' => 'The backups for :application_name are healthy', 25 | 'healthy_backup_found_body' => 'The backups for :application_name are considered healthy. Good job!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Important: The backups for :application_name are unhealthy', 28 | 'unhealthy_backup_found_subject_title' => 'Important: The backups for :application_name are unhealthy. :problem', 29 | 'unhealthy_backup_found_body' => 'The backups for :application_name on disk :disk_name are unhealthy.', 30 | 'unhealthy_backup_found_not_reachable' => 'The backup destination cannot be reached. :error', 31 | 'unhealthy_backup_found_empty' => 'There are no backups of this application at all.', 32 | 'unhealthy_backup_found_old' => 'The latest backup made on :date is considered too old.', 33 | 'unhealthy_backup_found_unknown' => 'Sorry, an exact reason cannot be determined.', 34 | 'unhealthy_backup_found_full' => 'The backups are using too much storage. Current usage is :disk_usage which is higher than the allowed limit of :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/es/notifications.php: -------------------------------------------------------------------------------- 1 | 'Mensaje de la excepción: :message', 5 | 'exception_trace' => 'Traza de la excepción: :trace', 6 | 'exception_message_title' => 'Mensaje de la excepción', 7 | 'exception_trace_title' => 'Traza de la excepción', 8 | 9 | 'backup_failed_subject' => 'Copia de seguridad de :application_name fallida', 10 | 'backup_failed_body' => 'Importante: Ocurrió un error al realizar la copia de seguridad de :application_name', 11 | 12 | 'backup_successful_subject' => 'Se completó con éxito la copia de seguridad de :application_name', 13 | 'backup_successful_subject_title' => '¡Nueva copia de seguridad creada con éxito!', 14 | 'backup_successful_body' => 'Buenas noticias, una nueva copia de seguridad de :application_name fue creada con éxito en el disco llamado :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'La limpieza de copias de seguridad de :application_name falló.', 17 | 'cleanup_failed_body' => 'Ocurrió un error mientras se realizaba la limpieza de copias de seguridad de :application_name', 18 | 19 | 'cleanup_successful_subject' => 'La limpieza de copias de seguridad de :application_name se completó con éxito', 20 | 'cleanup_successful_subject_title' => '!Limpieza de copias de seguridad completada con éxito!', 21 | 'cleanup_successful_body' => 'La limpieza de copias de seguridad de :application_name en el disco llamado :disk_name se completo con éxito.', 22 | 23 | 'healthy_backup_found_subject' => 'Las copias de seguridad de :application_name en el disco :disk_name están en buen estado', 24 | 'healthy_backup_found_subject_title' => 'Las copias de seguridad de :application_name están en buen estado', 25 | 'healthy_backup_found_body' => 'Las copias de seguridad de :application_name se consideran en buen estado. ¡Buen trabajo!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Importante: Las copias de seguridad de :application_name están en mal estado', 28 | 'unhealthy_backup_found_subject_title' => 'Importante: Las copias de seguridad de :application_name están en mal estado. :problem', 29 | 'unhealthy_backup_found_body' => 'Las copias de seguridad de :application_name en el disco :disk_name están en mal estado.', 30 | 'unhealthy_backup_found_not_reachable' => 'No se puede acceder al destino de la copia de seguridad. :error', 31 | 'unhealthy_backup_found_empty' => 'No existe ninguna copia de seguridad de esta aplicación.', 32 | 'unhealthy_backup_found_old' => 'La última copia de seguriad hecha en :date es demasiado antigua.', 33 | 'unhealthy_backup_found_unknown' => 'Lo siento, no es posible determinar la razón exacta.', 34 | 'unhealthy_backup_found_full' => 'Las copias de seguridad están ocupando demasiado espacio. El espacio utilizado actualmente es :disk_usage el cual es mayor que el límite permitido de :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/fa/notifications.php: -------------------------------------------------------------------------------- 1 | 'پیغام خطا: :message', 5 | 'exception_trace' => 'جزییات خطا: :trace', 6 | 'exception_message_title' => 'پیغام خطا', 7 | 'exception_trace_title' => 'جزییات خطا', 8 | 9 | 'backup_failed_subject' => 'پشتیبان‌گیری :application_name با خطا مواجه شد.', 10 | 'backup_failed_body' => 'پیغام مهم: هنگام پشتیبان‌گیری از :application_name خطایی رخ داده است. ', 11 | 12 | 'backup_successful_subject' => 'نسخه پشتیبان جدید :application_name با موفقیت ساخته شد.', 13 | 'backup_successful_subject_title' => 'پشتیبان‌گیری موفق!', 14 | 'backup_successful_body' => 'خبر خوب, به تازگی نسخه پشتیبان :application_name بر روی دیسک :disk_name با موفقیت ساخته شد. ', 15 | 16 | 'cleanup_failed_subject' => 'پاک‌‌سازی نسخه پشتیبان :application_name انجام نشد.', 17 | 'cleanup_failed_body' => 'هنگام پاک‌سازی نسخه پشتیبان :application_name خطایی رخ داده است.', 18 | 19 | 'cleanup_successful_subject' => 'پاک‌سازی نسخه پشتیبان :application_name با موفقیت انجام شد.', 20 | 'cleanup_successful_subject_title' => 'پاک‌سازی نسخه پشتیبان!', 21 | 'cleanup_successful_body' => 'پاک‌سازی نسخه پشتیبان :application_name بر روی دیسک :disk_name با موفقیت انجام شد.', 22 | 23 | 'healthy_backup_found_subject' => 'نسخه پشتیبان :application_name بر روی دیسک :disk_name سالم بود.', 24 | 'healthy_backup_found_subject_title' => 'نسخه پشتیبان :application_name سالم بود.', 25 | 'healthy_backup_found_body' => 'نسخه پشتیبان :application_name به نظر سالم میاد. دمت گرم!', 26 | 27 | 'unhealthy_backup_found_subject' => 'خبر مهم: نسخه پشتیبان :application_name سالم نبود.', 28 | 'unhealthy_backup_found_subject_title' => 'خبر مهم: نسخه پشتیبان :application_name سالم نبود. :problem', 29 | 'unhealthy_backup_found_body' => 'نسخه پشتیبان :application_name بر روی دیسک :disk_name سالم نبود.', 30 | 'unhealthy_backup_found_not_reachable' => 'مقصد پشتیبان‌گیری در دسترس نبود. :error', 31 | 'unhealthy_backup_found_empty' => 'برای این برنامه هیچ نسخه پشتیبانی وجود ندارد.', 32 | 'unhealthy_backup_found_old' => 'آخرین نسخه پشتیبان برای تاریخ :date است. که به نظر خیلی قدیمی میاد. ', 33 | 'unhealthy_backup_found_unknown' => 'متاسفانه دلیل دقیق مشخص نشده است.', 34 | 'unhealthy_backup_found_full' => 'نسخه‌های پشتیبانی که تهیه کرده اید حجم زیادی اشغال کرده اند. میزان دیسک استفاده شده :disk_usage است که از میزان مجاز :disk_limit فراتر رفته است. ', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/fi/notifications.php: -------------------------------------------------------------------------------- 1 | 'Virheilmoitus: :message', 5 | 'exception_trace' => 'Virhe, jäljitys: :trace', 6 | 'exception_message_title' => 'Virheilmoitus', 7 | 'exception_trace_title' => 'Virheen jäljitys', 8 | 9 | 'backup_failed_subject' => ':application_name varmuuskopiointi epäonnistui', 10 | 'backup_failed_body' => 'HUOM!: :application_name varmuuskoipionnissa tapahtui virhe', 11 | 12 | 'backup_successful_subject' => ':application_name varmuuskopioitu onnistuneesti', 13 | 'backup_successful_subject_title' => 'Uusi varmuuskopio!', 14 | 'backup_successful_body' => 'Hyviä uutisia! :application_name on varmuuskopioitu levylle :disk_name.', 15 | 16 | 'cleanup_failed_subject' => ':application_name varmuuskopioiden poistaminen epäonnistui.', 17 | 'cleanup_failed_body' => ':application_name varmuuskopioiden poistamisessa tapahtui virhe.', 18 | 19 | 'cleanup_successful_subject' => ':application_name varmuuskopiot poistettu onnistuneesti', 20 | 'cleanup_successful_subject_title' => 'Varmuuskopiot poistettu onnistuneesti!', 21 | 'cleanup_successful_body' => ':application_name varmuuskopiot poistettu onnistuneesti levyltä :disk_name.', 22 | 23 | 'healthy_backup_found_subject' => ':application_name varmuuskopiot levyllä :disk_name ovat kunnossa', 24 | 'healthy_backup_found_subject_title' => ':application_name varmuuskopiot ovat kunnossa', 25 | 'healthy_backup_found_body' => ':application_name varmuuskopiot ovat kunnossa. Hieno homma!', 26 | 27 | 'unhealthy_backup_found_subject' => 'HUOM!: :application_name varmuuskopiot ovat vialliset', 28 | 'unhealthy_backup_found_subject_title' => 'HUOM!: :application_name varmuuskopiot ovat vialliset. :problem', 29 | 'unhealthy_backup_found_body' => ':application_name varmuuskopiot levyllä :disk_name ovat vialliset.', 30 | 'unhealthy_backup_found_not_reachable' => 'Varmuuskopioiden kohdekansio ei ole saatavilla. :error', 31 | 'unhealthy_backup_found_empty' => 'Tästä sovelluksesta ei ole varmuuskopioita.', 32 | 'unhealthy_backup_found_old' => 'Viimeisin varmuuskopio, luotu :date, on liian vanha.', 33 | 'unhealthy_backup_found_unknown' => 'Virhe, tarkempaa tietoa syystä ei valitettavasti ole saatavilla.', 34 | 'unhealthy_backup_found_full' => 'Varmuuskopiot vievät liikaa levytilaa. Tällä hetkellä käytössä :disk_usage, mikä on suurempi kuin sallittu tilavuus (:disk_limit).', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/fr/notifications.php: -------------------------------------------------------------------------------- 1 | 'Message de l\'exception : :message', 5 | 'exception_trace' => 'Trace de l\'exception : :trace', 6 | 'exception_message_title' => 'Message de l\'exception', 7 | 'exception_trace_title' => 'Trace de l\'exception', 8 | 9 | 'backup_failed_subject' => 'Échec de la sauvegarde de :application_name', 10 | 'backup_failed_body' => 'Important : Une erreur est survenue lors de la sauvegarde de :application_name', 11 | 12 | 'backup_successful_subject' => 'Succès de la sauvegarde de :application_name', 13 | 'backup_successful_subject_title' => 'Sauvegarde créée avec succès !', 14 | 'backup_successful_body' => 'Bonne nouvelle, une nouvelle sauvegarde de :application_name a été créée avec succès sur le disque nommé :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Le nettoyage des sauvegardes de :application_name a echoué.', 17 | 'cleanup_failed_body' => 'Une erreur est survenue lors du nettoyage des sauvegardes de :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Succès du nettoyage des sauvegardes de :application_name', 20 | 'cleanup_successful_subject_title' => 'Sauvegardes nettoyées avec succès !', 21 | 'cleanup_successful_body' => 'Le nettoyage des sauvegardes de :application_name sur le disque nommé :disk_name a été effectué avec succès.', 22 | 23 | 'healthy_backup_found_subject' => 'Les sauvegardes pour :application_name sur le disque :disk_name sont saines', 24 | 'healthy_backup_found_subject_title' => 'Les sauvegardes pour :application_name sont saines', 25 | 'healthy_backup_found_body' => 'Les sauvegardes pour :application_name sont considérées saines. Bon travail !', 26 | 27 | 'unhealthy_backup_found_subject' => 'Important : Les sauvegardes pour :application_name sont corrompues', 28 | 'unhealthy_backup_found_subject_title' => 'Important : Les sauvegardes pour :application_name sont corrompues. :problem', 29 | 'unhealthy_backup_found_body' => 'Les sauvegardes pour :application_name sur le disque :disk_name sont corrompues.', 30 | 'unhealthy_backup_found_not_reachable' => 'La destination de la sauvegarde n\'est pas accessible. :error', 31 | 'unhealthy_backup_found_empty' => 'Il n\'y a aucune sauvegarde pour cette application.', 32 | 'unhealthy_backup_found_old' => 'La dernière sauvegarde du :date est considérée trop vieille.', 33 | 'unhealthy_backup_found_unknown' => 'Désolé, une raison exacte ne peut être déterminée.', 34 | 'unhealthy_backup_found_full' => 'Les sauvegardes utilisent trop d\'espace disque. L\'utilisation actuelle est de :disk_usage alors que la limite autorisée est de :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/hi/notifications.php: -------------------------------------------------------------------------------- 1 | 'गलती संदेश: :message', 5 | 'exception_trace' => 'गलती निशान: :trace', 6 | 'exception_message_title' => 'गलती संदेश', 7 | 'exception_trace_title' => 'गलती निशान', 8 | 9 | 'backup_failed_subject' => ':application_name का बैकअप असफल रहा', 10 | 'backup_failed_body' => 'जरूरी सुचना: :application_name का बैकअप लेते समय असफल रहे', 11 | 12 | 'backup_successful_subject' => ':application_name का बैकअप सफल रहा', 13 | 'backup_successful_subject_title' => 'बैकअप सफल रहा!', 14 | 'backup_successful_body' => 'खुशखबरी, :application_name का बैकअप :disk_name पर संग्रहित करने मे सफल रहे.', 15 | 16 | 'cleanup_failed_subject' => ':application_name के बैकअप की सफाई असफल रही.', 17 | 'cleanup_failed_body' => ':application_name के बैकअप की सफाई करते समय कुछ बाधा आयी है.', 18 | 19 | 'cleanup_successful_subject' => ':application_name के बैकअप की सफाई सफल रही', 20 | 'cleanup_successful_subject_title' => 'बैकअप की सफाई सफल रही!', 21 | 'cleanup_successful_body' => ':application_name का बैकअप जो :disk_name नाम की डिस्क पर संग्रहित है, उसकी सफाई सफल रही.', 22 | 23 | 'healthy_backup_found_subject' => ':disk_name नाम की डिस्क पर संग्रहित :application_name के बैकअप स्वस्थ है', 24 | 'healthy_backup_found_subject_title' => ':application_name के सभी बैकअप स्वस्थ है', 25 | 'healthy_backup_found_body' => 'बहुत बढ़िया! :application_name के सभी बैकअप स्वस्थ है.', 26 | 27 | 'unhealthy_backup_found_subject' => 'जरूरी सुचना : :application_name के बैकअप अस्वस्थ है', 28 | 'unhealthy_backup_found_subject_title' => 'जरूरी सुचना : :application_name के बैकअप :problem के बजेसे अस्वस्थ है', 29 | 'unhealthy_backup_found_body' => ':disk_name नाम की डिस्क पर संग्रहित :application_name के बैकअप अस्वस्थ है', 30 | 'unhealthy_backup_found_not_reachable' => ':error के बजेसे बैकअप की मंजिल तक पोहोच नहीं सकते.', 31 | 'unhealthy_backup_found_empty' => 'इस एप्लीकेशन का कोई भी बैकअप नहीं है.', 32 | 'unhealthy_backup_found_old' => 'हालहीमें :date को लिया हुआ बैकअप बहुत पुराना है.', 33 | 'unhealthy_backup_found_unknown' => 'माफ़ कीजिये, सही कारण निर्धारित नहीं कर सकते.', 34 | 'unhealthy_backup_found_full' => 'सभी बैकअप बहुत ज्यादा जगह का उपयोग कर रहे है. फ़िलहाल सभी बैकअप :disk_usage जगह का उपयोग कर रहे है, जो की :disk_limit अनुमति सीमा से अधिक का है.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/id/notifications.php: -------------------------------------------------------------------------------- 1 | 'Pesan pengecualian: :message', 5 | 'exception_trace' => 'Jejak pengecualian: :trace', 6 | 'exception_message_title' => 'Pesan pengecualian', 7 | 'exception_trace_title' => 'Jejak pengecualian', 8 | 9 | 'backup_failed_subject' => 'Gagal backup :application_name', 10 | 'backup_failed_body' => 'Penting: Sebuah error terjadi ketika membackup :application_name', 11 | 12 | 'backup_successful_subject' => 'Backup baru sukses dari :application_name', 13 | 'backup_successful_subject_title' => 'Backup baru sukses!', 14 | 'backup_successful_body' => 'Kabar baik, sebuah backup baru dari :application_name sukses dibuat pada disk bernama :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Membersihkan backup dari :application_name yang gagal.', 17 | 'cleanup_failed_body' => 'Sebuah error teradi ketika membersihkan backup dari :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Sukses membersihkan backup :application_name', 20 | 'cleanup_successful_subject_title' => 'Sukses membersihkan backup!', 21 | 'cleanup_successful_body' => 'Pembersihan backup :application_name pada disk bernama :disk_name telah sukses.', 22 | 23 | 'healthy_backup_found_subject' => 'Backup untuk :application_name pada disk :disk_name sehat', 24 | 'healthy_backup_found_subject_title' => 'Backup untuk :application_name sehat', 25 | 'healthy_backup_found_body' => 'Backup untuk :application_name dipertimbangkan sehat. Kerja bagus!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Penting: Backup untuk :application_name tidak sehat', 28 | 'unhealthy_backup_found_subject_title' => 'Penting: Backup untuk :application_name tidak sehat. :problem', 29 | 'unhealthy_backup_found_body' => 'Backup untuk :application_name pada disk :disk_name tidak sehat.', 30 | 'unhealthy_backup_found_not_reachable' => 'Tujuan backup tidak dapat terjangkau. :error', 31 | 'unhealthy_backup_found_empty' => 'Tidak ada backup pada aplikasi ini sama sekali.', 32 | 'unhealthy_backup_found_old' => 'Backup terakhir dibuat pada :date dimana dipertimbahkan sudah sangat lama.', 33 | 'unhealthy_backup_found_unknown' => 'Maaf, sebuah alasan persisnya tidak dapat ditentukan.', 34 | 'unhealthy_backup_found_full' => 'Backup menggunakan terlalu banyak kapasitas penyimpanan. Penggunaan terkini adalah :disk_usage dimana lebih besar dari batas yang diperbolehkan yaitu :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/it/notifications.php: -------------------------------------------------------------------------------- 1 | 'Messaggio dell\'eccezione: :message', 5 | 'exception_trace' => 'Traccia dell\'eccezione: :trace', 6 | 'exception_message_title' => 'Messaggio dell\'eccezione', 7 | 'exception_trace_title' => 'Traccia dell\'eccezione', 8 | 9 | 'backup_failed_subject' => 'Fallito il backup di :application_name', 10 | 'backup_failed_body' => 'Importante: Si è verificato un errore durante il backup di :application_name', 11 | 12 | 'backup_successful_subject' => 'Creato nuovo backup di :application_name', 13 | 'backup_successful_subject_title' => 'Nuovo backup creato!', 14 | 'backup_successful_body' => 'Grande notizia, un nuovo backup di :application_name è stato creato con successo sul disco :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Pulizia dei backup di :application_name fallita.', 17 | 'cleanup_failed_body' => 'Si è verificato un errore durante la pulizia dei backup di :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Pulizia dei backup di :application_name avvenuta con successo', 20 | 'cleanup_successful_subject_title' => 'Pulizia dei backup avvenuta con successo!', 21 | 'cleanup_successful_body' => 'La pulizia dei backup di :application_name sul disco :disk_name è avvenuta con successo.', 22 | 23 | 'healthy_backup_found_subject' => 'I backup per :application_name sul disco :disk_name sono sani', 24 | 'healthy_backup_found_subject_title' => 'I backup per :application_name sono sani', 25 | 'healthy_backup_found_body' => 'I backup per :application_name sono considerati sani. Bel Lavoro!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Importante: i backup per :application_name sono corrotti', 28 | 'unhealthy_backup_found_subject_title' => 'Importante: i backup per :application_name sono corrotti. :problem', 29 | 'unhealthy_backup_found_body' => 'I backup per :application_name sul disco :disk_name sono corrotti.', 30 | 'unhealthy_backup_found_not_reachable' => 'Impossibile raggiungere la destinazione di backup. :error', 31 | 'unhealthy_backup_found_empty' => 'Non esiste alcun backup di questa applicazione.', 32 | 'unhealthy_backup_found_old' => 'L\'ultimo backup fatto il :date è considerato troppo vecchio.', 33 | 'unhealthy_backup_found_unknown' => 'Spiacenti, non è possibile determinare una ragione esatta.', 34 | 'unhealthy_backup_found_full' => 'I backup utilizzano troppa memoria. L\'utilizzo corrente è :disk_usage che è superiore al limite consentito di :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/nl/notifications.php: -------------------------------------------------------------------------------- 1 | 'Fout bericht: :message', 5 | 'exception_trace' => 'Fout trace: :trace', 6 | 'exception_message_title' => 'Fout bericht', 7 | 'exception_trace_title' => 'Fout trace', 8 | 9 | 'backup_failed_subject' => 'Back-up van :application_name mislukt', 10 | 'backup_failed_body' => 'Belangrijk: Er ging iets fout tijdens het maken van een back-up van :application_name', 11 | 12 | 'backup_successful_subject' => 'Succesvolle nieuwe back-up van :application_name', 13 | 'backup_successful_subject_title' => 'Succesvolle nieuwe back-up!', 14 | 'backup_successful_body' => 'Goed nieuws, een nieuwe back-up van :application_name was succesvol aangemaakt op de schijf genaamd :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Het opschonen van de back-ups van :application_name is mislukt.', 17 | 'cleanup_failed_body' => 'Er ging iets fout tijdens het opschonen van de back-ups van :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Opschonen van :application_name back-ups was succesvol.', 20 | 'cleanup_successful_subject_title' => 'Opschonen van back-ups was succesvol!', 21 | 'cleanup_successful_body' => 'Het opschonen van de :application_name back-ups op de schijf genaamd :disk_name was succesvol.', 22 | 23 | 'healthy_backup_found_subject' => 'De back-ups voor :application_name op schijf :disk_name zijn gezond', 24 | 'healthy_backup_found_subject_title' => 'De back-ups voor :application_name zijn gezond', 25 | 'healthy_backup_found_body' => 'De back-ups voor :application_name worden als gezond beschouwd. Goed gedaan!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Belangrijk: De back-ups voor :application_name zijn niet meer gezond', 28 | 'unhealthy_backup_found_subject_title' => 'Belangrijk: De back-ups voor :application_name zijn niet gezond. :problem', 29 | 'unhealthy_backup_found_body' => 'De back-ups voor :application_name op schijf :disk_name zijn niet gezond.', 30 | 'unhealthy_backup_found_not_reachable' => 'De back-upbestemming kon niet worden bereikt. :error', 31 | 'unhealthy_backup_found_empty' => 'Er zijn geen back-ups van deze applicatie beschikbaar.', 32 | 'unhealthy_backup_found_old' => 'De laatste back-up gemaakt op :date is te oud.', 33 | 'unhealthy_backup_found_unknown' => 'Sorry, een exacte reden kon niet worden bepaald.', 34 | 'unhealthy_backup_found_full' => 'De back-ups gebruiken te veel opslagruimte. Momenteel wordt er :disk_usage gebruikt wat hoger is dan de toegestane limiet van :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/pl/notifications.php: -------------------------------------------------------------------------------- 1 | 'Błąd: :message', 5 | 'exception_trace' => 'Zrzut błędu: :trace', 6 | 'exception_message_title' => 'Błąd', 7 | 'exception_trace_title' => 'Zrzut błędu', 8 | 9 | 'backup_failed_subject' => 'Tworzenie kopii zapasowej aplikacji :application_name nie powiodło się', 10 | 'backup_failed_body' => 'Ważne: Wystąpił błąd podczas tworzenia kopii zapasowej aplikacji :application_name', 11 | 12 | 'backup_successful_subject' => 'Pomyślnie utworzono kopię zapasową aplikacji :application_name', 13 | 'backup_successful_subject_title' => 'Nowa kopia zapasowa!', 14 | 'backup_successful_body' => 'Wspaniała wiadomość, nowa kopia zapasowa aplikacji :application_name została pomyślnie utworzona na dysku o nazwie :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Czyszczenie kopii zapasowych aplikacji :application_name nie powiodło się.', 17 | 'cleanup_failed_body' => 'Wystąpił błąd podczas czyszczenia kopii zapasowej aplikacji :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Kopie zapasowe aplikacji :application_name zostały pomyślnie wyczyszczone', 20 | 'cleanup_successful_subject_title' => 'Kopie zapasowe zostały pomyślnie wyczyszczone!', 21 | 'cleanup_successful_body' => 'Czyszczenie kopii zapasowych aplikacji :application_name na dysku :disk_name zakończone sukcesem.', 22 | 23 | 'healthy_backup_found_subject' => 'Kopie zapasowe aplikacji :application_name na dysku :disk_name są poprawne', 24 | 'healthy_backup_found_subject_title' => 'Kopie zapasowe aplikacji :application_name są poprawne', 25 | 'healthy_backup_found_body' => 'Kopie zapasowe aplikacji :application_name są poprawne. Dobra robota!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Ważne: Kopie zapasowe aplikacji :application_name są niepoprawne', 28 | 'unhealthy_backup_found_subject_title' => 'Ważne: Kopie zapasowe aplikacji :application_name są niepoprawne. :problem', 29 | 'unhealthy_backup_found_body' => 'Kopie zapasowe aplikacji :application_name na dysku :disk_name są niepoprawne.', 30 | 'unhealthy_backup_found_not_reachable' => 'Miejsce docelowe kopii zapasowej nie jest osiągalne. :error', 31 | 'unhealthy_backup_found_empty' => 'W aplikacji nie ma żadnej kopii zapasowych tej aplikacji.', 32 | 'unhealthy_backup_found_old' => 'Ostatnia kopia zapasowa wykonania dnia :date jest zbyt stara.', 33 | 'unhealthy_backup_found_unknown' => 'Niestety, nie można ustalić dokładnego błędu.', 34 | 'unhealthy_backup_found_full' => 'Kopie zapasowe zajmują zbyt dużo miejsca. Obecne użycie dysku :disk_usage jest większe od ustalonego limitu :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/pt-BR/notifications.php: -------------------------------------------------------------------------------- 1 | 'Exception message: :message', 5 | 'exception_trace' => 'Exception trace: :trace', 6 | 'exception_message_title' => 'Exception message', 7 | 'exception_trace_title' => 'Exception trace', 8 | 9 | 'backup_failed_subject' => 'Falha no backup da aplicação :application_name', 10 | 'backup_failed_body' => 'Importante: Ocorreu um erro ao fazer o backup da aplicação :application_name', 11 | 12 | 'backup_successful_subject' => 'Backup realizado com sucesso: :application_name', 13 | 'backup_successful_subject_title' => 'Backup Realizado com sucesso!', 14 | 'backup_successful_body' => 'Boas notícias, um novo backup da aplicação :application_name foi criado no disco :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Falha na limpeza dos backups da aplicação :application_name.', 17 | 'cleanup_failed_body' => 'Um erro ocorreu ao fazer a limpeza dos backups da aplicação :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Limpeza dos backups da aplicação :application_name concluída!', 20 | 'cleanup_successful_subject_title' => 'Limpeza dos backups concluída!', 21 | 'cleanup_successful_body' => 'A limpeza dos backups da aplicação :application_name no disco :disk_name foi concluída.', 22 | 23 | 'healthy_backup_found_subject' => 'Os backups da aplicação :application_name no disco :disk_name estão em dia', 24 | 'healthy_backup_found_subject_title' => 'Os backups da aplicação :application_name estão em dia', 25 | 'healthy_backup_found_body' => 'Os backups da aplicação :application_name estão em dia. Bom trabalho!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Importante: Os backups da aplicação :application_name não estão em dia', 28 | 'unhealthy_backup_found_subject_title' => 'Importante: Os backups da aplicação :application_name não estão em dia. :problem', 29 | 'unhealthy_backup_found_body' => 'Os backups da aplicação :application_name no disco :disk_name não estão em dia.', 30 | 'unhealthy_backup_found_not_reachable' => 'O destino dos backups não pode ser alcançado. :error', 31 | 'unhealthy_backup_found_empty' => 'Não existem backups para essa aplicação.', 32 | 'unhealthy_backup_found_old' => 'O último backup realizado em :date é considerado muito antigo.', 33 | 'unhealthy_backup_found_unknown' => 'Desculpe, a exata razão não pode ser encontrada.', 34 | 'unhealthy_backup_found_full' => 'Os backups estão usando muito espaço de armazenamento. A utilização atual é de :disk_usage, o que é maior que o limite permitido de :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/ro/notifications.php: -------------------------------------------------------------------------------- 1 | 'Cu excepția mesajului: :message', 5 | 'exception_trace' => 'Urmă excepţie: :trace', 6 | 'exception_message_title' => 'Mesaj de excepție', 7 | 'exception_trace_title' => 'Urmă excepţie', 8 | 9 | 'backup_failed_subject' => 'Nu s-a putut face copie de rezervă pentru :application_name', 10 | 'backup_failed_body' => 'Important: A apărut o eroare în timpul generării copiei de rezervă pentru :application_name', 11 | 12 | 'backup_successful_subject' => 'Copie de rezervă efectuată cu succes pentru :application_name', 13 | 'backup_successful_subject_title' => 'O nouă copie de rezervă a fost efectuată cu succes!', 14 | 'backup_successful_body' => 'Vești bune, o nouă copie de rezervă pentru :application_name a fost creată cu succes pe discul cu numele :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Curățarea copiilor de rezervă pentru :application_name nu a reușit.', 17 | 'cleanup_failed_body' => 'A apărut o eroare în timpul curățirii copiilor de rezervă pentru :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Curățarea copiilor de rezervă pentru :application_name a fost făcută cu succes', 20 | 'cleanup_successful_subject_title' => 'Curățarea copiilor de rezervă a fost făcută cu succes!', 21 | 'cleanup_successful_body' => 'Curățarea copiilor de rezervă pentru :application_name de pe discul cu numele :disk_name a fost făcută cu succes.', 22 | 23 | 'healthy_backup_found_subject' => 'Copiile de rezervă pentru :application_name de pe discul :disk_name sunt în regulă', 24 | 'healthy_backup_found_subject_title' => 'Copiile de rezervă pentru :application_name sunt în regulă', 25 | 'healthy_backup_found_body' => 'Copiile de rezervă pentru :application_name sunt considerate în regulă. Bună treabă!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Important: Copiile de rezervă pentru :application_name nu sunt în regulă', 28 | 'unhealthy_backup_found_subject_title' => 'Important: Copiile de rezervă pentru :application_name nu sunt în regulă. :problem', 29 | 'unhealthy_backup_found_body' => 'Copiile de rezervă pentru :application_name de pe discul :disk_name nu sunt în regulă.', 30 | 'unhealthy_backup_found_not_reachable' => 'Nu se poate ajunge la destinația copiilor de rezervă. :error', 31 | 'unhealthy_backup_found_empty' => 'Nu există copii de rezervă ale acestei aplicații.', 32 | 'unhealthy_backup_found_old' => 'Cea mai recentă copie de rezervă făcută la :date este considerată prea veche.', 33 | 'unhealthy_backup_found_unknown' => 'Ne pare rău, un motiv exact nu poate fi determinat.', 34 | 'unhealthy_backup_found_full' => 'Copiile de rezervă folosesc prea mult spațiu de stocare. Utilizarea curentă este de :disk_usage care este mai mare decât limita permisă de :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/ru/notifications.php: -------------------------------------------------------------------------------- 1 | 'Сообщение об ошибке: :message', 5 | 'exception_trace' => 'Сведения об ошибке: :trace', 6 | 'exception_message_title' => 'Сообщение об ошибке', 7 | 'exception_trace_title' => 'Сведения об ошибке', 8 | 9 | 'backup_failed_subject' => 'Не удалось сделать резервную копию :application_name', 10 | 'backup_failed_body' => 'Внимание: Произошла ошибка во время резервного копирования :application_name', 11 | 12 | 'backup_successful_subject' => 'Успешно создана новая резервная копия :application_name', 13 | 'backup_successful_subject_title' => 'Успешно создана новая резервная копия!', 14 | 'backup_successful_body' => 'Отличная новость, новая резервная копия :application_name успешно создана и сохранена на диск :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Не удалось очистить резервные копии :application_name', 17 | 'cleanup_failed_body' => 'Произошла ошибка при очистке резервных копий :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Очистка от резервных копий :application_name прошла успешно', 20 | 'cleanup_successful_subject_title' => 'Очистка резервных копий прошла удачно!', 21 | 'cleanup_successful_body' => 'Очистка от старых резервных копий :application_name на диске :disk_name прошла удачно.', 22 | 23 | 'healthy_backup_found_subject' => 'Резервная копия :application_name с диска :disk_name установлена', 24 | 'healthy_backup_found_subject_title' => 'Резервная копия :application_name установлена', 25 | 'healthy_backup_found_body' => 'Резервная копия :application_name успешно установлена. Хорошая работа!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Внимание: резервная копия :application_name не установилась', 28 | 'unhealthy_backup_found_subject_title' => 'Внимание: резервная копия для :application_name не установилась. :problem', 29 | 'unhealthy_backup_found_body' => 'Резервная копия для :application_name на диске :disk_name не установилась.', 30 | 'unhealthy_backup_found_not_reachable' => 'Резервная копия не смогла установиться. :error', 31 | 'unhealthy_backup_found_empty' => 'Резервные копии для этого приложения отсутствуют.', 32 | 'unhealthy_backup_found_old' => 'Последнее резервное копирование создано :date является устаревшим.', 33 | 'unhealthy_backup_found_unknown' => 'Извините, точная причина не может быть определена.', 34 | 'unhealthy_backup_found_full' => 'Резервные копии используют слишком много памяти. Используется :disk_usage что выше допустимого предела: :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/tr/notifications.php: -------------------------------------------------------------------------------- 1 | 'Hata mesajı: :message', 5 | 'exception_trace' => 'Hata izleri: :trace', 6 | 'exception_message_title' => 'Hata mesajı', 7 | 'exception_trace_title' => 'Hata izleri', 8 | 9 | 'backup_failed_subject' => 'Yedeklenemedi :application_name', 10 | 'backup_failed_body' => 'Önemli: Yedeklenirken bir hata oluştu :application_name', 11 | 12 | 'backup_successful_subject' => 'Başarılı :application_name yeni yedeklemesi', 13 | 'backup_successful_subject_title' => 'Başarılı bir yeni yedekleme!', 14 | 'backup_successful_body' => 'Harika bir haber, :application_name âit yeni bir yedekleme :disk_name adlı diskte başarıyla oluşturuldu.', 15 | 16 | 'cleanup_failed_subject' => ':application_name yedeklemeleri temizlenmesi başarısız.', 17 | 'cleanup_failed_body' => ':application_name yedeklerini temizlerken bir hata oluştu ', 18 | 19 | 'cleanup_successful_subject' => ':application_name yedeklemeleri temizlenmesi başarılı.', 20 | 'cleanup_successful_subject_title' => 'Yedeklerin temizlenmesi başarılı!', 21 | 'cleanup_successful_body' => ':application_name yedeklemeleri temizlenmesi ,:disk_name diskinden silindi', 22 | 23 | 'healthy_backup_found_subject' => ':application_name yedeklenmesi ,:disk_name adlı diskte sağlıklı', 24 | 'healthy_backup_found_subject_title' => ':application_name yedeklenmesi sağlıklı', 25 | 'healthy_backup_found_body' => ':application_name için yapılan yedeklemeler sağlıklı sayılır. Aferin!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Önemli: :application_name için yedeklemeler sağlıksız', 28 | 'unhealthy_backup_found_subject_title' => 'Önemli: :application_name için yedeklemeler sağlıksız. :problem', 29 | 'unhealthy_backup_found_body' => 'Yedeklemeler: :application_name disk: :disk_name sağlıksız.', 30 | 'unhealthy_backup_found_not_reachable' => 'Yedekleme hedefine ulaşılamıyor. :error', 31 | 'unhealthy_backup_found_empty' => 'Bu uygulamanın yedekleri yok.', 32 | 'unhealthy_backup_found_old' => ':date tarihinde yapılan en son yedekleme çok eski kabul ediliyor.', 33 | 'unhealthy_backup_found_unknown' => 'Üzgünüm, kesin bir sebep belirlenemiyor.', 34 | 'unhealthy_backup_found_full' => 'Yedeklemeler çok fazla depolama alanı kullanıyor. Şu anki kullanım: :disk_usage, izin verilen sınırdan yüksek: :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/uk/notifications.php: -------------------------------------------------------------------------------- 1 | 'Повідомлення про помилку: :message', 5 | 'exception_trace' => 'Деталі помилки: :trace', 6 | 'exception_message_title' => 'Повідомлення помилки', 7 | 'exception_trace_title' => 'Деталі помилки', 8 | 9 | 'backup_failed_subject' => 'Не вдалось зробити резервну копію :application_name', 10 | 'backup_failed_body' => 'Увага: Трапилась помилка під час резервного копіювання :application_name', 11 | 12 | 'backup_successful_subject' => 'Успішне резервне копіювання :application_name', 13 | 'backup_successful_subject_title' => 'Успішно створена резервна копія!', 14 | 'backup_successful_body' => 'Чудова новина, нова резервна копія :application_name успішно створена і збережена на диск :disk_name.', 15 | 16 | 'cleanup_failed_subject' => 'Не вдалось очистити резервні копії :application_name', 17 | 'cleanup_failed_body' => 'Сталася помилка під час очищення резервних копій :application_name', 18 | 19 | 'cleanup_successful_subject' => 'Успішне очищення від резервних копій :application_name', 20 | 'cleanup_successful_subject_title' => 'Очищення резервних копій пройшло вдало!', 21 | 'cleanup_successful_body' => 'Очищенно від старих резервних копій :application_name на диску :disk_name пойшло успішно.', 22 | 23 | 'healthy_backup_found_subject' => 'Резервна копія :application_name з диску :disk_name установлена', 24 | 'healthy_backup_found_subject_title' => 'Резервна копія :application_name установлена', 25 | 'healthy_backup_found_body' => 'Резервна копія :application_name успішно установлена. Хороша робота!', 26 | 27 | 'unhealthy_backup_found_subject' => 'Увага: резервна копія :application_name не установилась', 28 | 'unhealthy_backup_found_subject_title' => 'Увага: резервна копія для :application_name не установилась. :problem', 29 | 'unhealthy_backup_found_body' => 'Резервна копія для :application_name на диску :disk_name не установилась.', 30 | 'unhealthy_backup_found_not_reachable' => 'Резервна копія не змогла установитись. :error', 31 | 'unhealthy_backup_found_empty' => 'Резервні копії для цього додатку відсутні.', 32 | 'unhealthy_backup_found_old' => 'Останнє резервне копіювання створено :date є застарілим.', 33 | 'unhealthy_backup_found_unknown' => 'Вибачте, але ми не змогли визначити точну причину.', 34 | 'unhealthy_backup_found_full' => 'Резервні копії використовують занадто багато пам`яті. Використовується :disk_usage що вище за допустиму межу :disk_limit.', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/zh-CN/notifications.php: -------------------------------------------------------------------------------- 1 | '异常信息: :message', 5 | 'exception_trace' => '异常跟踪: :trace', 6 | 'exception_message_title' => '异常信息', 7 | 'exception_trace_title' => '异常跟踪', 8 | 9 | 'backup_failed_subject' => ':application_name 备份失败', 10 | 'backup_failed_body' => '重要说明:备份 :application_name 时发生错误', 11 | 12 | 'backup_successful_subject' => ':application_name 备份成功', 13 | 'backup_successful_subject_title' => '备份成功!', 14 | 'backup_successful_body' => '好消息, :application_name 备份成功,位于磁盘 :disk_name 中。', 15 | 16 | 'cleanup_failed_subject' => '清除 :application_name 的备份失败。', 17 | 'cleanup_failed_body' => '清除备份 :application_name 时发生错误', 18 | 19 | 'cleanup_successful_subject' => '成功清除 :application_name 的备份', 20 | 'cleanup_successful_subject_title' => '成功清除备份!', 21 | 'cleanup_successful_body' => '成功清除 :disk_name 磁盘上 :application_name 的备份。', 22 | 23 | 'healthy_backup_found_subject' => ':disk_name 磁盘上 :application_name 的备份是健康的', 24 | 'healthy_backup_found_subject_title' => ':application_name 的备份是健康的', 25 | 'healthy_backup_found_body' => ':application_name 的备份是健康的。干的好!', 26 | 27 | 'unhealthy_backup_found_subject' => '重要说明::application_name 的备份不健康', 28 | 'unhealthy_backup_found_subject_title' => '重要说明::application_name 备份不健康。 :problem', 29 | 'unhealthy_backup_found_body' => ':disk_name 磁盘上 :application_name 的备份不健康。', 30 | 'unhealthy_backup_found_not_reachable' => '无法访问备份目标。 :error', 31 | 'unhealthy_backup_found_empty' => '根本没有此应用程序的备份。', 32 | 'unhealthy_backup_found_old' => '最近的备份创建于 :date ,太旧了。', 33 | 'unhealthy_backup_found_unknown' => '对不起,确切原因无法确定。', 34 | 'unhealthy_backup_found_full' => '备份占用了太多存储空间。当前占用了 :disk_usage ,高于允许的限制 :disk_limit。', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/lang/vendor/backup/zh-TW/notifications.php: -------------------------------------------------------------------------------- 1 | '異常訊息: :message', 5 | 'exception_trace' => '異常追蹤: :trace', 6 | 'exception_message_title' => '異常訊息', 7 | 'exception_trace_title' => '異常追蹤', 8 | 9 | 'backup_failed_subject' => ':application_name 備份失敗', 10 | 'backup_failed_body' => '重要說明:備份 :application_name 時發生錯誤', 11 | 12 | 'backup_successful_subject' => ':application_name 備份成功', 13 | 'backup_successful_subject_title' => '備份成功!', 14 | 'backup_successful_body' => '好消息, :application_name 備份成功,位於磁盤 :disk_name 中。', 15 | 16 | 'cleanup_failed_subject' => '清除 :application_name 的備份失敗。', 17 | 'cleanup_failed_body' => '清除備份 :application_name 時發生錯誤', 18 | 19 | 'cleanup_successful_subject' => '成功清除 :application_name 的備份', 20 | 'cleanup_successful_subject_title' => '成功清除備份!', 21 | 'cleanup_successful_body' => '成功清除 :disk_name 磁盤上 :application_name 的備份。', 22 | 23 | 'healthy_backup_found_subject' => ':disk_name 磁盤上 :application_name 的備份是健康的', 24 | 'healthy_backup_found_subject_title' => ':application_name 的備份是健康的', 25 | 'healthy_backup_found_body' => ':application_name 的備份是健康的。幹的好!', 26 | 27 | 'unhealthy_backup_found_subject' => '重要說明::application_name 的備份不健康', 28 | 'unhealthy_backup_found_subject_title' => '重要說明::application_name 備份不健康。 :problem', 29 | 'unhealthy_backup_found_body' => ':disk_name 磁盤上 :application_name 的備份不健康。', 30 | 'unhealthy_backup_found_not_reachable' => '無法訪問備份目標。 :error', 31 | 'unhealthy_backup_found_empty' => '根本沒有此應用程序的備份。', 32 | 'unhealthy_backup_found_old' => '最近的備份創建於 :date ,太舊了。', 33 | 'unhealthy_backup_found_unknown' => '對不起,確切原因無法確定。', 34 | 'unhealthy_backup_found_full' => '備份佔用了太多存儲空間。當前佔用了 :disk_usage ,高於允許的限制 :disk_limit。', 35 | ]; 36 | -------------------------------------------------------------------------------- /resources/sass/app.scss: -------------------------------------------------------------------------------- 1 | // 2 | -------------------------------------------------------------------------------- /resources/views/auth/reset_password.blade.php: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Laravel Starter 8 | 9 | 10 | 11 | 12 | 13 | 70 | 71 | 72 |
73 |
74 |

Forgot Password?

75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 |
83 |
84 | 85 | 86 | -------------------------------------------------------------------------------- /resources/views/welcome.blade.php: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Laravel 8 | 9 | 10 | 11 | 12 | 13 | 65 | 66 | 67 |
68 | @if (Route::has('login')) 69 | 80 | @endif 81 | 82 |
83 |
84 | Laravel 85 |
86 | 87 | 97 |
98 |
99 | 100 | 101 | -------------------------------------------------------------------------------- /routes/api.php: -------------------------------------------------------------------------------- 1 | get('/user', function (Request $request) { 18 | return $request->user(); 19 | }); 20 | 21 | Route::middleware(['api'])->group(function ($router) { 22 | Route::post('login', 'AuthController@login'); 23 | Route::post('logout', 'AuthController@logout'); 24 | Route::post('refresh', 'AuthController@refresh'); 25 | Route::get('me', 'AuthController@me')->middleware('log.route'); 26 | 27 | Route::post('register', 'RegistrationController@register'); 28 | Route::get('email/verify/{id}', 'VerificationController@verify')->name('verification.verify'); 29 | Route::get('email/resend', 'VerificationController@resend')->name('verification.resend'); 30 | Route::post('password/email', 'ForgotPasswordController@forgot'); 31 | Route::post('password/reset', 'ForgotPasswordController@reset'); 32 | 33 | Route::patch('user/profile', 'UserController@updateProfile'); 34 | }); 35 | -------------------------------------------------------------------------------- /routes/channels.php: -------------------------------------------------------------------------------- 1 | id === (int) $id; 18 | }); 19 | -------------------------------------------------------------------------------- /routes/console.php: -------------------------------------------------------------------------------- 1 | comment(Inspiring::quote()); 19 | })->describe('Display an inspiring quote'); 20 | -------------------------------------------------------------------------------- /routes/web.php: -------------------------------------------------------------------------------- 1 | name('password.reset'); 21 | -------------------------------------------------------------------------------- /server.php: -------------------------------------------------------------------------------- 1 | 8 | */ 9 | 10 | $uri = urldecode( 11 | parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH) 12 | ); 13 | 14 | // This file allows us to emulate Apache's "mod_rewrite" functionality from the 15 | // built-in PHP web server. This provides a convenient way to test a Laravel 16 | // application without having installed a "real" web server software here. 17 | if ($uri !== '/' && file_exists(__DIR__.'/public'.$uri)) { 18 | return false; 19 | } 20 | 21 | require_once __DIR__.'/public/index.php'; 22 | -------------------------------------------------------------------------------- /serverless.yml: -------------------------------------------------------------------------------- 1 | service: laravel-starter-serverless 2 | 3 | provider: 4 | name: aws 5 | region: ap-south-1 6 | runtime: provided 7 | 8 | plugins: 9 | - ./vendor/bref/bref 10 | 11 | package: 12 | exclude: 13 | - node_modules/** 14 | - public/storage 15 | - resources/assets/** 16 | - storage/** 17 | - tests/** 18 | 19 | functions: 20 | website: 21 | handler: public/index.php 22 | timeout: 28 # in seconds (API Gateway has a timeout of 29 seconds) 23 | layers: 24 | - ${bref:layer.php-73-fpm} 25 | events: 26 | - http: 'ANY /' 27 | - http: 'ANY /{proxy+}' 28 | artisan: 29 | handler: artisan 30 | timeout: 120 # in seconds 31 | layers: 32 | - ${bref:layer.php-73} # PHP 33 | - ${bref:layer.console} # The "console" layer 34 | worker: 35 | handler: worker.php 36 | layers: 37 | - ${bref:layer.php-73} 38 | events: 39 | # Declares that our worker is triggered by jobs in SQS 40 | - sqs: 41 | arn: !GetAtt AlertQueue.Arn 42 | # If you create the queue manually, the line above could be: 43 | # arn: 'arn:aws:sqs:us-east-1:1234567890:my_sqs_queue' 44 | # Only 1 item at a time to simplify error handling 45 | batchSize: 1 46 | 47 | resources: 48 | Resources: 49 | # The SQS queue 50 | AlertQueue: 51 | Type: AWS::SQS::Queue 52 | Properties: 53 | RedrivePolicy: 54 | maxReceiveCount: 3 # jobs will be retried up to 3 times 55 | # Failed jobs (after the retries) will be moved to the other queue for storage 56 | deadLetterTargetArn: !GetAtt DeadLetterQueue.Arn 57 | 58 | # Failed jobs will go into that SQS queue to be stored, until a developer looks at these errors 59 | DeadLetterQueue: 60 | Type: AWS::SQS::Queue 61 | Properties: 62 | MessageRetentionPeriod: 1209600 # maximum retention: 14 days 63 | -------------------------------------------------------------------------------- /storage/app/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !public/ 3 | !.gitignore 4 | -------------------------------------------------------------------------------- /storage/app/public/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /storage/framework/.gitignore: -------------------------------------------------------------------------------- 1 | config.php 2 | routes.php 3 | schedule-* 4 | compiled.php 5 | services.json 6 | events.scanned.php 7 | routes.scanned.php 8 | down 9 | -------------------------------------------------------------------------------- /storage/framework/cache/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !data/ 3 | !.gitignore 4 | -------------------------------------------------------------------------------- /storage/framework/cache/data/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /storage/framework/sessions/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /storage/framework/testing/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /storage/framework/views/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /storage/logs/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore 3 | -------------------------------------------------------------------------------- /tests/CreatesApplication.php: -------------------------------------------------------------------------------- 1 | make(Kernel::class)->bootstrap(); 19 | 20 | return $app; 21 | } 22 | } 23 | -------------------------------------------------------------------------------- /tests/Feature/ExampleTest.php: -------------------------------------------------------------------------------- 1 | get('/'); 18 | 19 | $response->assertStatus(200); 20 | } 21 | } 22 | -------------------------------------------------------------------------------- /tests/Feature/UsersTest.php: -------------------------------------------------------------------------------- 1 | $this->faker->name]; 18 | 19 | $this->patchJson('api/user/profile', $attributes, ['Authorization' => "bearer $token"]) 20 | ->assertStatus(200); 21 | 22 | $this->assertDatabaseHas($user->getTable(), array_merge($attributes, [ 23 | 'id' => $user->id 24 | ])); 25 | } 26 | } 27 | -------------------------------------------------------------------------------- /tests/TestCase.php: -------------------------------------------------------------------------------- 1 | artisan('migrate'); 16 | $this->artisan('db:seed'); 17 | 18 | $this->withoutExceptionHandling(); 19 | } 20 | } 21 | -------------------------------------------------------------------------------- /tests/Unit/ExampleTest.php: -------------------------------------------------------------------------------- 1 | assertTrue(true); 17 | } 18 | } 19 | -------------------------------------------------------------------------------- /webpack.mix.js: -------------------------------------------------------------------------------- 1 | const mix = require('laravel-mix'); 2 | 3 | /* 4 | |-------------------------------------------------------------------------- 5 | | Mix Asset Management 6 | |-------------------------------------------------------------------------- 7 | | 8 | | Mix provides a clean, fluent API for defining some Webpack build steps 9 | | for your Laravel application. By default, we are compiling the Sass 10 | | file for the application as well as bundling up all the JS files. 11 | | 12 | */ 13 | 14 | mix.js('resources/js/app.js', 'public/js') 15 | .sass('resources/sass/app.scss', 'public/css'); 16 | -------------------------------------------------------------------------------- /worker.php: -------------------------------------------------------------------------------- 1 | make(Illuminate\Contracts\Console\Kernel::class); 11 | $kernel->bootstrap(); 12 | 13 | return $app->makeWith(LaravelSqsHandler::class, [ 14 | 'connection' => 'sqs', // this is the Laravel Queue connection 15 | 'queue' => getenv('SQS_QUEUE'), 16 | ]); 17 | --------------------------------------------------------------------------------