Question Your experience with using the "GIT" extension?

[Bitpalast]

The GIT extension is a nice feature for subscriptions. But is it sufficient for users to use the extension in the GUI only? When a user accesses SSH in their chrooted environment, they cannot use the command line git. Who has experience with using GIT only in the Plesk GUI (the webspace control panel)? Is the command line git needed for everyday tasks or can - in your opinion - everything that you need be done in the Plesk GUI, too?

 

[IgorG]

What about git CLI utility git: Git Repositories ?
Is it useful to you?

 

[Bitpalast]

Not for the customers at least, because with chrooted SSH they cannot access the git command line utility. We had previously tested the "git" repository on some installations. Customer who were using it did ask for command line git access. We are now in the process to decide whether we want to officially offer "git support" in our webhosting plans. But the question is whether the GUI git component is enough for someone who expects "git support" or whether users will expect a command line utitility, too, or actually "need" that for what they typically do.

 

[futureweb]

What we miss most is "https auth" for GIT Repos and the disability to change SSH Port for SSH Keys Auth ...

Since we trigger Updates by Web-Hook from Atlassian Bitbucket - we don't need the GIT GUI in Plesk much more than for first setup ... ;-)