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

Issue Composer Path Mismatch in Plesk Git Deployment

naseremad

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.64
When deploying a Laravel project through Plesk's Git integration, there is a path mismatch for the `composer.json` file due to a project structure change. The system is still referencing the old composer path (`/core/composer.json`) instead of the updated path (`folder/composer.json`). This occurs when the "Install composer.json dependencies" option is enabled during Git deployment.

Technical Details
- Original Path: `/core/composer.json`
- New Path: `folder/composer.json`
- Affected Systems**:
- Plesk Git Integration
- Laravel Project
- Composer Dependency Management

Problem Impact
This path mismatch prevents proper dependency installation during the deployment process, as the system cannot locate the `composer.json` file at the expected location.

Any suggestions regarding a solution?
 
Back
Top