• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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