The Difference Between SFTP and Git Based Deployments

SFTP and Git based deployments both have their pros and cons.

SFTP works on the widest variety of servers, and is by far the easiest setup option. The biggest downside to SFTP is that it takes longer to push large updates to your server. We recommend SFTP deployments if you're running your site on a shared web hosting provider or if you are just getting started with Git.

Git-based deployments, on the other hand, deploy very quickly and give you considerably more control. However, they require more setup and provide more opportunity for mistakes if you don't configure things correctly. We don't recommend this deployment type for beginners. Also, setup may be complicated or not possible on shared hosting providers.

Why deploy using SFTP?

SFTP is the easiest deployment option, because nearly every web server should support it, whether you use a shared host or a dedicated server. It only requires enabling SSH access for your hosting account (not all hosting companies turn it on by default), but once it’s enabled the process is straight-forward.

When a deployment is initiated, REPOMAN.IO will get the latest files from the Git repository and copy those files to the server of your choice.

Read the SFTP Setup Guide

Back to top

Why deploy using Git?

If you have experience using Git and run your website on a VPS or at a hosting company that lets you install Git on their servers, you might be best served by choosing Git as your deployment method.

With Git installed on your server, REPOMAN.IO simply executes a list of commands that you have pre-defined, pulling the files directly from Github and executing whatever commands or scripts you have defined. This makes your deployments both faster and more flexible. For example, in addition to pulling the updates from git you might also want to trigger database updates or clear cache.

Read the Git Setup Guide

Back to top