• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question How to add Git to live site.

Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.56 #2
I have been tasked with adding new features to a Plesk site which is already live. There is no Git integration; to date updates have been deployed by FTP.

How can I begin using Git deployments for a site which is already live?

I do have an exact copy of the site in a Git repo, which I can attach to the Plesk site. However, what happens the first time I click the 'Deploy now' button? I assume my entire live site will be overwritten by the repo files, which in theory should be an exact copy. But, it this doesn't go well, the site will go down!

What is the risk-free process for introducing Git deployments to a Plesk site which is already live?

Chris.
 
I don't know the direct answer to your question. However, why not make a copy of the site on another (sub)domain for testing purposes and try to see what happens?
 
In tests everything works perfectly. However I'd like to see some official Plesk guidance, if it exists, on my scenario to reduce risk when I do this on the Production site.
 
Back
Top