Articles in this section

See more

How to enable Queues in the Laravel project for Plesk Laravel Toolkit

Avatar
Ivan Postnikov
Updated
Follow
DoNotDelete:docref kb: how-to

Question

How to enable Queues in the Laravel project for Plesk Laravel Toolkit?

Answer

Before you start, make sure the following is true:

  • The latest version of the Laravel Toolkit is installed from the Extensions Catalog. Queues are supported in version 1.4.2-218 or later.
  • Laravel version 7.x or later is installed. To check the current Laravel version, run php artisan -V to check it.

To enable Queues in the Laravel project, do the following:

  1. Make sure that scheduled tasks for Laravel project are enabled.
  2. Integrate the Laravel package into Plesk. In your Git project, in the “composer.json” file, add the following lines:

    CONFIG_TEXT: "require": {
    . . .
    "plesk/ext-laravel-integration": "*"
    }

    Warning: In case a local repository is used, and changes are performed via File Manager, it is required to commit changes by performing step 5 from this article.  To avoid overwriting after deploy.

  3. Re-deploy project at example.com > Manage Laravel application > Deployment, and then click Deploy.
  4. Select the database you want to process the queues. Depending on the chosen database, follow one of the scenarios below:

     For MySQL database:

      1. Create the database
      2. In the “.env” project file, add the following lines:

          CONFIG_TEXT: DB_CONNECTION=mysql
          DB_HOST=<actual db_host (might be localhost)>
          QUEUE_CONNECTION=database
          DB_DATABASE=<from step 3.1.1>
          DB_USERNAME=<from step 3.1.1>
          DB_PASSWORD=<from step 3.1.1>

    NOTE: Instead of `database_host`, `database_name`, `database_username`, and `database_password`, specify those you have used while creating the database during step 1.

      3. Create the necessary tables in the database. Go to example.com > Manage Laravel Application > Artisan, and then run the migrate command.

      For sqlite3 database:
      1. Create a .sqlite3 database file, for example, test.sqlite3.
      2. In the .env project file, add the following lines:

         CONFIG_TEXT: DB_CONNECTION=sqlite
         QUEUE_CONNECTION=database
         DB_DATABASE=<path_to_sqlite3> started website docroot

      3. Go to example.com > manage laravel application > Artisan execute php artisan queue:table
      4. Go to example.com > manage laravel application > Artisan execute migrate to create necessary tables in the database

Comments

4 comments

Sort by Date Votes
  • Avatar
    Mario Küpfer (Edited )

    This change throws an error on all existing projects that do not have the corresponding package installed:
    There are no commands defined in the "plesk-ext-laravel" namespace.

    [2023-01-26T13:21:00.443049+00:00] production.ERROR: There are no commands defined in the "plesk-ext-laravel" namespace. {"exception":"[object] (Symfony\Component\Console\Exception\NamespaceNotFoundException(code: 0): There are no commands defined in the "plesk-ext-laravel" namespace. at /var/www/vhosts/***redacted***/application/vendor/symfony/console/Application.php:632)"} []
    1
    Comment actions Permalink
  • Avatar
    Mario Küpfer (Edited )

    Ensure you not run "php artisan optimize" during deployment. Otherwise the toggle is deactivated.

    0
    Comment actions Permalink
  • Avatar
    Martin Allen

    Seeing the same issue - looks like it might be occurring when artisan schedule:run is being called each minute??

     There are no commands defined in the "plesk-ext-laravel" namespace
    [2023-01-27 15:09:44] development.ERROR: There are no commands defined in the "plesk-ext-laravel" namespace. {"exception":"[object]

    (Symfony\\Component\\Console\\Exception\\NamespaceNotFoundException(code:

    0): There are no commands defined in the \"plesk-ext-laravel\"

    namespace. at

    /var/www/vhosts/xxxxx/vendor/symfony/console/Application.php:624)

    [stacktrace]

    #0

    /var/www/vhosts/xxxxx/vendor/symfony/console/Application.php(675):

    Symfony\\Component\\Console\\Application->findNamespace()

    #1

    /var/www/vhosts/xxxxx/vendor/symfony/console/Application.php(259):

    Symfony\\Component\\Console\\Application->find()

    #2

    /var/www/vhosts/xxxxx/vendor/symfony/console/Application.php(171):

    Symfony\\Component\\Console\\Application->doRun()

    #3

    /var/www/vhosts/xxxxx/vendor/laravel/framework/src/Illuminate/Console/Application.php(111):

    Symfony\\Component\\Console\\Application->run()

    #4

    /var/www/vhosts/xxxxx/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(155):

    Illuminate\\Console\\Application->run()

    #5 /var/www/vhosts/xxxxxx/artisan(37):

    Illuminate\\Foundation\\Console\\Kernel->handle()

    #6 {main}

    "}
    0
    Comment actions Permalink
  • Avatar
    Ken Cline

    Yep. It's broken. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles