diff --git a/eloquent-serialization.md b/eloquent-serialization.md index 48d6860617..fff46dce58 100644 --- a/eloquent-serialization.md +++ b/eloquent-serialization.md @@ -34,7 +34,7 @@ You may also convert entire [collections](/docs/{{version}}/eloquent-collections ### Serializing To JSON -To convert a model to JSON, you should use the `toJson` method. Like `toArray`, the `toJson` method is recursive, so all attributes and relations will be converted to JSON. You may also specify JSON encoding options [supported by PHP](http://php.net/manual/en/function.json-encode.php): +To convert a model to JSON, you should use the `toJson` method. Like `toArray`, the `toJson` method is recursive, so all attributes and relations will be converted to JSON. You may also specify JSON encoding options [supported by PHP](https://secure.php.net/manual/en/function.json-encode.php): $user = App\User::find(1); diff --git a/hashing.md b/hashing.md index 9e6af1a3c7..42bd0eb960 100644 --- a/hashing.md +++ b/hashing.md @@ -67,7 +67,7 @@ If you are using the Argon2 algorithm, the `make` method allows you to manage th 'threads' => 2, ]); -> {tip} For more information on these options, check out the [official PHP documentation](http://php.net/manual/en/function.password-hash.php). +> {tip} For more information on these options, check out the [official PHP documentation](https://secure.php.net/manual/en/function.password-hash.php). #### Verifying A Password Against A Hash diff --git a/mix.md b/mix.md index fc9023ed33..84f9d7442a 100644 --- a/mix.md +++ b/mix.md @@ -101,7 +101,7 @@ If you need to override the [underlying Less plug-in options](https://github.com ### Sass -The `sass` method allows you to compile [Sass](http://sass-lang.com/) into CSS. You may use the method like so: +The `sass` method allows you to compile [Sass](https://sass-lang.com/) into CSS. You may use the method like so: mix.sass('resources/sass/app.scss', 'public/css'); @@ -134,7 +134,7 @@ You may also install additional Stylus plug-ins, such as [Rupture](https://githu ### PostCSS -[PostCSS](http://postcss.org/), a powerful tool for transforming your CSS, is included with Laravel Mix out of the box. By default, Mix leverages the popular [Autoprefixer](https://github.com/postcss/autoprefixer) plug-in to automatically apply all necessary CSS3 vendor prefixes. However, you're free to add any additional plug-ins that are appropriate for your application. First, install the desired plug-in through NPM and then reference it in your `webpack.mix.js` file: +[PostCSS](https://postcss.org/), a powerful tool for transforming your CSS, is included with Laravel Mix out of the box. By default, Mix leverages the popular [Autoprefixer](https://github.com/postcss/autoprefixer) plug-in to automatically apply all necessary CSS3 vendor prefixes. However, you're free to add any additional plug-ins that are appropriate for your application. First, install the desired plug-in through NPM and then reference it in your `webpack.mix.js` file: mix.sass('resources/sass/app.scss', 'public/css') .options({ diff --git a/requests.md b/requests.md index 917d2dd6bc..e2e82337ae 100644 --- a/requests.md +++ b/requests.md @@ -118,7 +118,7 @@ The `method` method will return the HTTP verb for the request. You may use the ` ### PSR-7 Requests -The [PSR-7 standard](http://www.php-fig.org/psr/psr-7/) specifies interfaces for HTTP messages, including requests and responses. If you would like to obtain an instance of a PSR-7 request instead of a Laravel request, you will first need to install a few libraries. Laravel uses the *Symfony HTTP Message Bridge* component to convert typical Laravel requests and responses into PSR-7 compatible implementations: +The [PSR-7 standard](https://www.php-fig.org/psr/psr-7/) specifies interfaces for HTTP messages, including requests and responses. If you would like to obtain an instance of a PSR-7 request instead of a Laravel request, you will first need to install a few libraries. Laravel uses the *Symfony HTTP Message Bridge* component to convert typical Laravel requests and responses into PSR-7 compatible implementations: composer require symfony/psr-http-message-bridge composer require zendframework/zend-diactoros @@ -345,7 +345,7 @@ The `UploadedFile` class also contains methods for accessing the file's fully-qu #### Other File Methods -There are a variety of other methods available on `UploadedFile` instances. Check out the [API documentation for the class](http://api.symfony.com/3.0/Symfony/Component/HttpFoundation/File/UploadedFile.html) for more information regarding these methods. +There are a variety of other methods available on `UploadedFile` instances. Check out the [API documentation for the class](https://api.symfony.com/3.0/Symfony/Component/HttpFoundation/File/UploadedFile.html) for more information regarding these methods. ### Storing Uploaded Files @@ -400,7 +400,7 @@ To solve this, you may use the `App\Http\Middleware\TrustProxies` middleware tha protected $headers = Request::HEADER_X_FORWARDED_ALL; } -> {tip} If you are using AWS Elastic Load Balancing, your `$headers` value should be `Request::HEADER_X_FORWARDED_AWS_ELB`. For more information on the constants that may be used in the `$headers` property, check out Symfony's documentation on [trusting proxies](http://symfony.com/doc/current/deployment/proxies.html). +> {tip} If you are using AWS Elastic Load Balancing, your `$headers` value should be `Request::HEADER_X_FORWARDED_AWS_ELB`. For more information on the constants that may be used in the `$headers` property, check out Symfony's documentation on [trusting proxies](https://symfony.com/doc/current/deployment/proxies.html). #### Trusting All Proxies diff --git a/scheduling.md b/scheduling.md index a3e70b1c49..db6a3aa5c1 100644 --- a/scheduling.md +++ b/scheduling.md @@ -67,7 +67,7 @@ You may define all of your scheduled tasks in the `schedule` method of the `App\ } } -In addition to scheduling using Closures, you may also use [invokable objects](http://php.net/manual/en/language.oop5.magic.php#object.invoke). Invokable objects are simple PHP classes that contain an `__invoke` method: +In addition to scheduling using Closures, you may also use [invokable objects](https://secure.php.net/manual/en/language.oop5.magic.php#object.invoke). Invokable objects are simple PHP classes that contain an `__invoke` method: $schedule->call(new DeleteRecentUsers)->daily(); diff --git a/structure.md b/structure.md index 944b14ee67..069c4ccbd7 100644 --- a/structure.md +++ b/structure.md @@ -103,7 +103,7 @@ The `vendor` directory contains your [Composer](https://getcomposer.org) depende ## The App Directory -The majority of your application is housed in the `app` directory. By default, this directory is namespaced under `App` and is autoloaded by Composer using the [PSR-4 autoloading standard](http://www.php-fig.org/psr/psr-4/). +The majority of your application is housed in the `app` directory. By default, this directory is namespaced under `App` and is autoloaded by Composer using the [PSR-4 autoloading standard](https://www.php-fig.org/psr/psr-4/). The `app` directory contains a variety of additional directories such as `Console`, `Http`, and `Providers`. Think of the `Console` and `Http` directories as providing an API into the core of your application. The HTTP protocol and CLI are both mechanisms to interact with your application, but do not actually contain application logic. In other words, they are two ways of issuing commands to your application. The `Console` directory contains all of your Artisan commands, while the `Http` directory contains your controllers, middleware, and requests. diff --git a/valet.md b/valet.md index 0177396f9b..45e84cc103 100644 --- a/valet.md +++ b/valet.md @@ -33,7 +33,7 @@ Out of the box, Valet support includes, but is not limited to: - [Contao](https://contao.org/en/) - [Craft](https://craftcms.com) - [Drupal](https://www.drupal.org/) -- [Jigsaw](http://jigsaw.tighten.co) +- [Jigsaw](https://jigsaw.tighten.co) - [Joomla](https://www.joomla.org/) - [Katana](https://github.com/themsaid/katana) - [Kirby](https://getkirby.com/) @@ -55,17 +55,17 @@ However, you may extend Valet with your own [custom drivers](#custom-valet-drive As you may know, Laravel offers [Homestead](/docs/{{version}}/homestead), another local Laravel development environment. Homestead and Valet differ in regards to their intended audience and their approach to local development. Homestead offers an entire Ubuntu virtual machine with automated Nginx configuration. Homestead is a wonderful choice if you want a fully virtualized Linux development environment or are on Windows / Linux. -Valet only supports Mac, and requires you to install PHP and a database server directly onto your local machine. This is easily achieved by using [Homebrew](http://brew.sh/) with commands like `brew install php` and `brew install mysql`. Valet provides a blazing fast local development environment with minimal resource consumption, so it's great for developers who only require PHP / MySQL and do not need a fully virtualized development environment. +Valet only supports Mac, and requires you to install PHP and a database server directly onto your local machine. This is easily achieved by using [Homebrew](https://brew.sh/) with commands like `brew install php` and `brew install mysql`. Valet provides a blazing fast local development environment with minimal resource consumption, so it's great for developers who only require PHP / MySQL and do not need a fully virtualized development environment. Both Valet and Homestead are great choices for configuring your Laravel development environment. Which one you choose will depend on your personal taste and your team's needs. ## Installation -**Valet requires macOS and [Homebrew](http://brew.sh/). Before installation, you should make sure that no other programs such as Apache or Nginx are binding to your local machine's port 80.** +**Valet requires macOS and [Homebrew](https://brew.sh/). Before installation, you should make sure that no other programs such as Apache or Nginx are binding to your local machine's port 80.**
-- Install or update [Homebrew](http://brew.sh/) to the latest version using `brew update`. +- Install or update [Homebrew](https://brew.sh/) to the latest version using `brew update`. - Install PHP 7.3 using Homebrew via `brew install php`. - Install [Composer](https://getcomposer.org). - Install Valet with Composer via `composer global require laravel/valet`. Make sure the `~/.composer/vendor/bin` directory is in your system's "PATH".