• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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