• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Input Laravel ToolKit: Add option to run npm install and npm run build when installing a new Laravel application.

progr2lovatel

New Pleskian
When I deploy a Laravel application to Plesk, I always use the Laravel ToolKit extension. I follow all the steps outlined in the documentation to install my application. However, at the end of the deployment process, I still need to go to the Node tab of the extension and run the npm install and npm run build commands. It would be nice if these steps could already be integrated into the Laravel ToolKit extension deployment process.
 
Hello, @progr2lovatel. Thank you for your input. Given that, this is not required for all sites out team hasn't considered integrating it directly into deployment process. There is a deployment script implementation that could be configured for this specific scenario. Still, please do not hesitate to open a new UserVoice suggestion - if there is interest by other users our team will definitely take the idea into consideration.
 
Hello, @progr2lovatel. Thank you for your input. Given that, this is not required for all sites out team hasn't considered integrating it directly into deployment process. There is a deployment script implementation that could be configured for this specific scenario. Still, please do not hesitate to open a new UserVoice suggestion - if there is interest by other users our team will definitely take the idea into consideration.
First of all, thank you for your attention. Yes, I understand what you meant @Sebahat.hadzhi. But I imagine having an option on this screen where we Laravel users can implement a custom script before the first deployment. But this is just a suggestion in case someone has a different idea feel free to discuss about it.

plesk.png
 
Back
Top