• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved Application installation problems with Laravel Tookit

Ratto

New Pleskian
Server operating system version
AlmaLinux 8.7
Plesk version and microupdate number
18.0.49 Update #2
While installing the application with the Laravel Toolkit, in the "Configuring the Laravel Application" step the toolkit copies the .env.example file to the .env.

In my opinion this is an error because the .env.example file, obtained from the git repository, must not contain production credentials.

By the way, if I create the .env file manually, it gets overwritten o_O


Is there a solution to this? I don't understand why the toolkit deals with this thing.
 
Back
Top