• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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