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

[Manu7]

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?

 

[yspirin]

There is workaround

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

 

[Ratto]

It's incredible that they haven't fixed this problem yet

 

[Janus Bahs Jacquet]

There seem to be virtually no resources on this online, and every single resource I can find blindly assumes Linux hosting where there’s an SQLite database at /opt/psa/var/modules/laravel/laravel_toolkit.sqlite3.

What is the Windows equivalent of this?!

 

[Janus Bahs Jacquet]

Okay, a full search for laravel_toolkit on the C drive finally found it: it’s located at C:\Program Files (x86)\Plesk\var\modules\laravel\laravel_toolkit.sqlite3.

You’ll need to [download the SQLite CLI tools](https://sqlite.org/download.html) for your version of Windows and then run that in the command prompt to open the file.