Php artisan optimizes time only on composer installation

Question

I am running a laravel application on Azure. Things are moving in the right direction; the composer's installation was not used for work at all. However, the php artisan optimize command is now disabled:

However, running "php artisan optimize" alone does not present a problem:

What could be the reason for this?

Edit:

Removing the symfony folder does not help, it is not there when I run the "Composer install" command:

Increasing the timeout does not help either, I increased it both in the azure and in the composer.json file:

This still gives me a wait time after installing symfony components:

...

Answer 1

When I deployed a new Laravel 5 application for Azure Web applications and tried to reproduce your problem, however, it worked fine on my side, either I run the php artisan optimize command, either composer install or composer update .

I installed the composer in Site Extensions on the website of the KUDU console application in Azure Web applications, the URL should look like this: https://<your_site_name>.scm.azurewebsites.net/SiteExtensions/#gallery

There are several solutions of other developers that are facing you in the same problem, you can try the following solutions:

• try increasing max_execution_time or set to 0, refer to https://azure.microsoft.com/en-us/documentation/articles/web-sites-php-configure/#how-to-change-the-built-in-php -configurations to change embedded PHP configurations on Azure Web Apps. And you can change the process-timeout file in Composer.json :

  "config" : { "process-timeout": 0 }

• delete the entire symfony folder and try again. How did the comments on PHP Artisan Optimize come out? # 1050 , it seems like symfony issues are raising the problem.

Answer 2

@Rkey, In my experience, I think the problem is more related to the version / configuration of the symphony. I suggest you remove / modify the symphony configuration from the composer.lock file (NOTE: please backup this file, if you cannot succeed, you can also restore your environment). And then you can run this "composer install" .

After installing the component, you will see a warning window that shows that

 your session is timeout, please refresh your browser. 

You can see this information because the server is in the initialization process. Any problems, please feel free to let me know.

Answer 3

I also have this problem. Did updating the plan help?

According to this, upgrading to S3 helps ... I have not tried it yet ... Let me know if this really works.

Answer 4

@Rkey and @cabs, in my understanding on this issue, I want to note that the composer is not fully supported by Azure. The problem is that it uses the Taskkill command, which is locked on Azure. We are aware of this and please feel free to submit an idea or suggestion based on experience with Azure at https://feedback.azure.com/forums/34192--general-feedback .

Answer 5

I am also stuck in this problem for a week. We tried all the solutions on the forum, but did not have time. This morning we finally decided after reinstalling XAMPP. This was a problem in my previous version of PHP 5.6.19. When using the new XAMPP with PHP version 5.6.28, it worked fine.