Friday, 27 September 2013

Deployment best practices on production without GIT

Deployment best practices on production without GIT

I have a Production server that I currently deploy my code manually with
sftp. I'd like to improve this deployment process but the Production
server does not have GIT installed and installing is not an option at this
time.
I'm looking for advice on best practices and common tools to make my
deployments simple, mistake proof and partially automated.
I have develop and master branches in my GIT repo. Master branch is always
an exact replica of the Production server. Whenever I'm happy with the
state of develop, I merge changes into master, lookup the list of files
that changed and manually copy them over via sftp.
I would like to improve this process and do following:
Go and create some sort of backup of the live site's main folder.
Have some script that automatically checks what changed in masters last
commit and uploads files via ssh to the Production server.
Allows me to revert back changes is something went wrong (hence step 1)
Are there tools, scripts or procedures you use to do something similar?
Thanks?

No comments:

Post a Comment