Support Git push / pull to remote via SSH
The current Git Deployment feature is great but doesn't support committing and pushing changes back to the remote repo. Files are changed when new plugins are installed or media is uploaded and these files will be excluded from the repo if they aren't committed and pushed.
Users could bypass the Git Deployment feature all together and use native Git via SSH if they were allowed access to the .ssh folder. However in order to push and pull to a remote repo via SSH, Git needs to write to the .ssh folder which you forbid. I understand you don't want to give users root access but allowing them to access .ssh folder would be harmless.
Yaron Guez
shared this idea
With the new credentials system (http://www.cloudways.com/blog/old-ssh-sftp-user-to-the-new-credentials-system/) recently deployed, you can now use all git functionality via command line (push, pull, clone …).
This will work ONLY for master credentials (https://support.cloudways.com/difference-between-master-credentials-and-application-credentials/) as team members don’t have SSH access anymore.
With master user now, you can create your own .ssh folder, so all git options should be unlocked.
Please note this refers to git execution from the command line and is different from the basic Git Deployment feature integrated with our console (https://support.cloudways.com/using-git-for-deployment/), that will just pull a remote repository from the console, store it locally on the server and sync it with the public_html folder of your application and is aimed at users with basic git needs and not comfortable with the command line.
Cloudways Team
-
fgilio
commented
Awesome, thanks!
-
AdminCloudways
(Admin, Cloudways)
commented
With the new credentials system (http://www.cloudways.com/blog/old-ssh-sftp-user-to-the-new-credentials-system/) recently deployed, you can now use all git functionality via command line (push, pull, clone ...).
This will work ONLY for master credentials (https://support.cloudways.com/difference-between-master-credentials-and-application-credentials/) as team members don't have SSH access anymore.
With master user now, you can create your own .ssh folder, so all git options should be unlocked.
Please note this refers to git execution from the command line and is different from the basic Git Deployment feature integrated with our console (https://support.cloudways.com/using-git-for-deployment/), that will just pull a remote repository from the console, store it locally on the server and sync it with the public_html folder of your application and is aimed at users with basic git needs and not comfortable with the command line.
Cloudways Team
-
Cubiq Design
commented
We are a Digital Agency that also require this.
We are intending to move the majority of our sites to Cloudways, but without SSH Access that allows native Git, we can't take that step.
It's vital to our workflow.
-
Anonymous
commented
Would really love this feature. I use Cloudways for all of my personal and freelance client sites and not being able to push or pull from the command line really slows down my workflow.
I would love to convince the agency that I work for to move from wpEngine to Cloudways because, after using the two extensively, I much prefer cloudways, however there is no way a team of 4+ developers all working on the same projects could make the switch without this feature.
-
akhbar
commented
My company was about to use your service but this is really a showstopper for us.
Unfortunately we can't. The application deployment is a complex process which needs to use command line. -
Neil C Smith
commented
We'd really like this for the workflow we're currently looking at, with dev site on one CW instance, and staging / production on another - similar to https://www.drupal.org/node/803746
Having live sites properly under version control is also an extra way of checking for tampering.
This would also allow for other uses of SSH outside git, which would be great for looking at cron scripts for offsite backup (the one feature we find lacking currently).