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

Question Laravel Toolkit: Changing git repository on existing application breaks deployment

Manu7

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
18.0.51 Update #1
Hello Everyone

I've attempted to change the Git repository for an existing Laravel application that was connected and managed by the Plesk Laravel Toolkit.

The goal was to move from a local repository to a remote one hosting the same codebase.

I deleted the old repository and added the new one, but now the "Deployment" tab in the Laravel Toolkit is gone for that domain. Additionally, all the toolkit-provided tasks on deployment are no longer executed (e.g., maintenance mode, composer install, etc.).

Is there a way to "reconnect" the toolkit to a new repository?
 
There is workaround
Code:
sqlite3 /opt/psa/var/modules/laravel/laravel_toolkit.sqlite3
sqlite> select repoName from applications where domainId = <domain id>;
You will get a response like this 'laravel_2efa6e'

Go to Domain -> Git -> Repository settings
Set to 'Repository name' received value

repository_settings.jpg
 
Back
Top