• 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.

Question Laravel Toolkit Production-ready

NormanHuth

New Pleskian
Server operating system version
DEBIAN
Plesk version and microupdate number
Plesk Obsidian 18.0.46 Update #1
Is there somewhere an overview of what is fixed and developed with the plugin?

With scheduled tasks must be careful. If you have multiple Laravel installations on one domain & subdomains only 1 task will be created. Would be great if such things also work and no need to do this manually for each subdomain.
Of course, that's annoying if you don't know that. I wonder why nothing is updated, the sctipt simply creates a task despite several separate installations.

And why is it not possible to disable "Install composer.json dependencies"?
For production, "composer install --optimize-autoloader --no-dev" is correct. But what if you want to set up a test installation and install the DEV requirements as well?

And will the toolkit eventually use Supervisors as queue worker?
 
Back
Top