• 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!
  • 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 Upgrading GIT under PLESK - official way

Kurt Ludikovsky

Basic Pleskian
What is the official way to upgrade GIT in PLESK (Obsidian).

GIT download says the latest version is 2.30.0

The GIT Extension in PLESK reports 1.2.0-252 (in PLESK Obsidian 18.0.33)

git --version report "git version 2.11.0"

And in the Plesk Obsidian Releases (Resolved - Plesk Obsidian Releases) it states
(Windows) Updated Git to version 2.29.2.3.


As Git is an extension to PLESK Obsidian, what is the officially recommended way for upgrading git?

I am asking this question especially due to the effect that some upgrades have to be taken with care, as they have side effects to PLESK, (eg. updates to MariaDB), and therefore require specific handling
 
Last edited:
Back
Top