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

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