Git vs FTP for web deployment [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

I know what git is for and how to use it, (a little bit) but there is one concept I still don’t fully understand. I have heard a lot of web developers lately saying that they use git for every web project even though they are not collaborating, they just use git as an FTP alternative, in fact they claim that FTP is an old method to upload your sites.

My question is, how could I use git to upload my site without having to pay for a service such as beanstalk?

Is really FTP considered an old technology and we should be using git?

Thanks a lot

Answer 1

Using your favourite version control is the only sensible way to deploy anything.

Git is not only about collaboration and distributed VCS it is also a serverless VCS (by definition) - so you can deploy from your dev machine to your deployment target.

To summarise when setup properly to deploy your changes is as simple as;

git push hub master

For more information A web-focused Git workflow and Using Git for Deployment

I'm not going to answer the subjective bit of the question; there are a myriad of reasons why I'd deprecate FTP - but it is a valid way of transferring files as long as you understand the limitations of the technology.

I will however say that you absolutely must be using version control within your deployment strategy.

Answer 2

See the following links for instructions on how to deploy a Git repo to your server:

• Deploy your site with git
• How to deploy your code from GitHub automatically
• A web-focused Git workflow