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

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