• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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