• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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