Cara menggunakan php command not found

Question

Laravel Sail is a light-weight command-line interface for interacting with Laravel's default Docker development environment. Sail provides a great starting point for building a Laravel application using PHP, MySQL, and Redis without requiring prior Docker experience.

At its heart, Sail is the

php artisan sail:install --devcontainer

8 file and the

php artisan sail:install --devcontainer

9 script that is stored at the root of your project. The

php artisan sail:install --devcontainer

9 script provides a CLI with convenient methods for interacting with the Docker containers defined by the

php artisan sail:install --devcontainer

8 file.

Laravel Sail is supported on macOS, Linux, and Windows (via WSL2).

Installation & Setup

Laravel Sail is automatically installed with all new Laravel applications so you may start using it immediately. To learn how to create a new Laravel application, please consult Laravel's installation documentation for your operating system. During installation, you will be asked to choose which Sail supported services your application will be interacting with.

Installing Sail Into Existing Applications

If you are interested in using Sail with an existing Laravel application, you may simply install Sail using the Composer package manager. Of course, these steps assume that your existing local development environment allows you to install Composer dependencies:

composer require laravel/sail --dev

After Sail has been installed, you may run the

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

2 Artisan command. This command will publish Sail's

php artisan sail:install --devcontainer

8 file to the root of your application:

Finally, you may start Sail. To continue learning how to use Sail, please continue reading the remainder of this documentation:

Using Devcontainers

If you would like to develop within a Devcontainer, you may provide the

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

4 option to the

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

2 command. The

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

4 option will instruct the

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

2 command to publish a default

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

8 file to the root of your application:

php artisan sail:install --devcontainer

Configuring A Shell Alias

By default, Sail commands are invoked using the

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

9 script that is included with all new Laravel applications:

However, instead of repeatedly typing

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

9 to execute Sail commands, you may wish to configure a shell alias that allows you to execute Sail's commands more easily:

alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail'

To make sure this is always available, you may add this to your shell configuration file in your home directory, such as

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

1 or

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

2, and then restart your shell.

Once the shell alias has been configured, you may execute Sail commands by simply typing

php artisan sail:install --devcontainer

9. The remainder of this documentation's examples will assume that you have configured this alias:

Starting & Stopping Sail

Laravel Sail's

php artisan sail:install --devcontainer

8 file defines a variety of Docker containers that work together to help you build Laravel applications. Each of these containers is an entry within the

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

5 configuration of your

php artisan sail:install --devcontainer

8 file. The

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

7 container is the primary application container that will be serving your application.

Before starting Sail, you should ensure that no other web servers or databases are running on your local computer. To start all of the Docker containers defined in your application's

php artisan sail:install --devcontainer

8 file, you should execute the

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

9 command:

To start all of the Docker containers in the background, you may start Sail in "detached" mode:

Once the application's containers have been started, you may access the project in your web browser at: http://localhost.

To stop all of the containers, you may simply press Control + C to stop the container's execution. Or, if the containers are running in the background, you may use the

sail composer require laravel/sanctum

0 command:

Executing Commands

When using Laravel Sail, your application is executing within a Docker container and is isolated from your local computer. However, Sail provides a convenient way to run various commands against your application such as arbitrary PHP commands, Artisan commands, Composer commands, and Node / NPM commands.

When reading the Laravel documentation, you will often see references to Composer, Artisan, and Node / NPM commands that do not reference Sail. Those examples assume that these tools are installed on your local computer. If you are using Sail for your local Laravel development environment, you should execute those commands using Sail:

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

Executing PHP Commands

PHP commands may be executed using the

sail composer require laravel/sanctum

1 command. Of course, these commands will execute using the PHP version that is configured for your application. To learn more about the PHP versions available to Laravel Sail, consult the :

Executing Composer Commands

Composer commands may be executed using the

sail composer require laravel/sanctum

2 command. Laravel Sail's application container includes a Composer 2.x installation:

sail composer require laravel/sanctum

Installing Composer Dependencies For Existing Applications

If you are developing an application with a team, you may not be the one that initially creates the Laravel application. Therefore, none of the application's Composer dependencies, including Sail, will be installed after you clone the application's repository to your local computer.

You may install the application's dependencies by navigating to the application's directory and executing the following command. This command uses a small Docker container containing PHP and Composer to install the application's dependencies:

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

When using the

sail composer require laravel/sanctum

3 image, you should use the same version of PHP that you plan to use for your application (

sail composer require laravel/sanctum

4,

sail composer require laravel/sanctum

5,

sail composer require laravel/sanctum

6, or

sail composer require laravel/sanctum

7).

Executing Artisan Commands

Laravel Artisan commands may be executed using the

sail composer require laravel/sanctum

8 command:

Executing Node / NPM Commands

Node commands may be executed using the

sail composer require laravel/sanctum

9 command while NPM commands may be executed using the

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

0 command:

If you wish, you may use Yarn instead of NPM:

Interacting With Databases

MySQL

As you may have noticed, your application's

php artisan sail:install --devcontainer

8 file contains an entry for a MySQL container. This container uses a Docker volume so that the data stored in your database is persisted even when stopping and restarting your containers.

In addition, the first time the MySQL container starts, it will create two databases for you. The first database is named using the value of your

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

2 environment variable and is for your local development. The second is a dedicated testing database named

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

3 and will ensure that your tests do not interfere with your development data.

Once you have started your containers, you may connect to the MySQL instance within your application by setting your

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

4 environment variable within your application's

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

5 file to

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

6.

To connect to your application's MySQL database from your local machine, you may use a graphical database management application such as TablePlus. By default, the MySQL database is accessible at

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

7 port 3306.

Redis

Your application's

php artisan sail:install --devcontainer

8 file also contains an entry for a Redis container. This container uses a Docker volume so that the data stored in your Redis data is persisted even when stopping and restarting your containers. Once you have started your containers, you may connect to the Redis instance within your application by setting your

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

9 environment variable within your application's

    -v "$(pwd):/var/www/html" \



 laravelsail/php82-composer:latest \
 composer install --ignore-platform-reqs

5 file to

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

1.

To connect to your application's Redis database from your local machine, you may use a graphical database management application such as TablePlus. By default, the Redis database is accessible at

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

7 port 6379.

MeiliSearch

If you chose to install the MeiliSearch service when installing Sail, your application's

php artisan sail:install --devcontainer

8 file will contain an entry for this powerful search-engine that is compatible with Laravel Scout. Once you have started your containers, you may connect to the MeiliSearch instance within your application by setting your

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

4 environment variable to

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

5.

From your local machine, you may access MeiliSearch's web based administration panel by navigating to

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

6 in your web browser.

File Storage

If you plan to use Amazon S3 to store files while running your application in its production environment, you may wish to install the MinIO service when installing Sail. MinIO provides an S3 compatible API that you may use to develop locally using Laravel's

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

7 file storage driver without creating "test" storage buckets in your production S3 environment. If you choose to install MinIO while installing Sail, a MinIO configuration section will be added to your application's

php artisan sail:install --devcontainer

8 file.

By default, your application's

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

9 configuration file already contains a disk configuration for the

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

7 disk. In addition to using this disk to interact with Amazon S3, you may use it to interact with any S3 compatible file storage service such as MinIO by simply modifying the associated environment variables that control its configuration. For example, when using MinIO, your filesystem environment variable configuration should be defined as follows:

AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

In order for Laravel's Flysystem integration to generate proper URLs when using MinIO, you should define the

AWS_URL=http://localhost:9000/local

1 environment variable so that it matches your application's local URL and includes the bucket name in the URL path:

AWS_URL=http://localhost:9000/local

You may create buckets via the MinIO console, which is available at

AWS_URL=http://localhost:9000/local

2. The default username for the MinIO console is

php artisan sail:install --devcontainer

9 while the default password is

AWS_URL=http://localhost:9000/local

4.

Warning
Generating temporary storage URLs via the
AWS_URL=http://localhost:9000/local
5 method is not supported when using MinIO.

Running Tests

Laravel provides amazing testing support out of the box, and you may use Sail's

AWS_URL=http://localhost:9000/local

6 command to run your applications feature and unit tests. Any CLI options that are accepted by PHPUnit may also be passed to the

AWS_URL=http://localhost:9000/local

6 command:

The Sail

AWS_URL=http://localhost:9000/local

6 command is equivalent to running the

AWS_URL=http://localhost:9000/local

6 Artisan command:

By default, Sail will create a dedicated

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

3 database so that your tests do not interfere with the current state of your database. In a default Laravel installation, Sail will also configure your

1 file to use this database when executing your tests:

Laravel Dusk

Laravel Dusk provides an expressive, easy-to-use browser automation and testing API. Thanks to Sail, you may run these tests without ever installing Selenium or other tools on your local computer. To get started, uncomment the Selenium service in your application's

php artisan sail:install --devcontainer

8 file:

    image: 'selenium/standalone-chrome'

Next, ensure that the

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

7 service in your application's

php artisan sail:install --devcontainer

8 file has a

5 entry for

6:

Finally, you may run your Dusk test suite by starting Sail and running the

7 command:

Selenium On Apple Silicon

If your local machine contains an Apple Silicon chip, your

6 service must use the

9 image:

php artisan sail:install --devcontainer

0

Previewing Emails

Laravel Sail's default

php artisan sail:install --devcontainer

8 file contains a service entry for MailHog. MailHog intercepts emails sent by your application during local development and provides a convenient web interface so that you can preview your email messages in your browser. When using Sail, MailHog's default host is

    image: 'selenium/standalone-chrome'

1 and is available via port 1025:

When Sail is running, you may access the MailHog web interface at: http://localhost:8025

Container CLI

Sometimes you may wish to start a Bash session within your application's container. You may use the

    image: 'selenium/standalone-chrome'

2 command to connect to your application's container, allowing you to inspect its files and installed services as well execute arbitrary shell commands within the container:

To start a new Laravel Tinker session, you may execute the

    image: 'selenium/standalone-chrome'

3 command:

PHP Versions

Sail currently supports serving your application via PHP 8.2, 8.1, PHP 8.0, or PHP 7.4. The default PHP version used by Sail is currently PHP 8.2. To change the PHP version that is used to serve your application, you should update the

    image: 'selenium/standalone-chrome'

4 definition of the

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

7 container in your application's

php artisan sail:install --devcontainer

8 file:

php artisan sail:install --devcontainer

1

In addition, you may wish to update your

    image: 'selenium/standalone-chrome'

7 name to reflect the version of PHP being used by your application. This option is also defined in your application's

php artisan sail:install --devcontainer

8 file:

After updating your application's

php artisan sail:install --devcontainer

8 file, you should rebuild your container images:

Node Versions

Sail installs Node 18 by default. To change the Node version that is installed when building your images, you may update the

php artisan sail:install --devcontainer

00 definition of the

# Running Artisan commands locally...
# Running Artisan commands within Laravel Sail...

7 service in your application's

php artisan sail:install --devcontainer

8 file:

After updating your application's

php artisan sail:install --devcontainer

8 file, you should rebuild your container images:

Sometimes you may need to share your site publicly in order to preview your site for a colleague or to test webhook integrations with your application. To share your site, you may use the

php artisan sail:install --devcontainer

04 command. After executing this command, you will be issued a random

php artisan sail:install --devcontainer

05 URL that you may use to access your application:

When sharing your site via the

php artisan sail:install --devcontainer

04 command, you should configure your application's trusted proxies within the

php artisan sail:install --devcontainer

07 middleware. Otherwise, URL generation helpers such as

php artisan sail:install --devcontainer

08 and

php artisan sail:install --devcontainer

09 will be unable to determine the correct HTTP host that should be used during URL generation:

php artisan sail:install --devcontainer

2

If you would like to choose the subdomain for your shared site, you may provide the

php artisan sail:install --devcontainer

10 option when executing the

php artisan sail:install --devcontainer

04 command:

php artisan sail:install --devcontainer

3

Note
The
php artisan sail:install --devcontainer
04 command is powered by Expose, an open source tunneling service by BeyondCode.

Debugging With Xdebug

Laravel Sail's Docker configuration includes support for Xdebug, a popular and powerful debugger for PHP. In order to enable Xdebug, you will need to add a few variables to your application's

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

5 file to . To enable Xdebug you must set the appropriate mode(s) before starting Sail:

php artisan sail:install --devcontainer

4

Linux Host IP Configuration

Internally, the

php artisan sail:install --devcontainer

14 environment variable is defined as

php artisan sail:install --devcontainer

15 so that Xdebug will be properly configured for Mac and Windows (WSL2). If your local machine is running Linux, you should ensure that you are running Docker Engine 17.06.0+ and Compose 1.16.0+. Otherwise, you will need to manually define this environment variable as shown below.

First, you should determine the correct host IP address to add to the environment variable by running the following command. Typically, the

php artisan sail:install --devcontainer

16 should be the name of the container that serves your application and often ends with

php artisan sail:install --devcontainer

17:

php artisan sail:install --devcontainer

5

Once you have obtained the correct host IP address, you should define the

php artisan sail:install --devcontainer

18 variable within your application's

    -v "$(pwd):/var/www/html" \
    laravelsail/php82-composer:latest \
    composer install --ignore-platform-reqs

5 file:

php artisan sail:install --devcontainer

6

Xdebug CLI Usage

A

php artisan sail:install --devcontainer

20 command may be used to start a debugging session when running an Artisan command:

php artisan sail:install --devcontainer

7

Xdebug Browser Usage

To debug your application while interacting with the application via a web browser, follow the for initiating an Xdebug session from the web browser.

If you're using PhpStorm, please review JetBrain's documentation regarding zero-configuration debugging.

Warning
Laravel Sail relies on
php artisan sail:install --devcontainer
21 to serve your application. The
php artisan sail:install --devcontainer
21 command only accepts the
php artisan sail:install --devcontainer
14 and
php artisan sail:install --devcontainer
24 variables as of Laravel version 8.53.0. Older versions of Laravel (8.52.0 and below) do not support these variables and will not accept debug connections.

Customization

Since Sail is just Docker, you are free to customize nearly everything about it. To publish Sail's own Dockerfiles, you may execute the

php artisan sail:install --devcontainer

25 command:

After running this command, the Dockerfiles and other configuration files used by Laravel Sail will be placed within a

php artisan sail:install --devcontainer

26 directory in your application's root directory. After customizing your Sail installation, you may wish to change the image name for the application container in your application's

php artisan sail:install --devcontainer

8 file. After doing so, rebuild your application's containers using the

    image: 'selenium/standalone-chrome'

4 command. Assigning a unique name to the application image is particularly important if you are using Sail to develop multiple Laravel applications on a single machine:

kode php