• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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