Why you should not use git for deployment

Deployment has always been hard and there has always been the problem on how do you transfer your files from one place to another and be sure that they are 100% the same.

Here are the drawbacks when using git

1. It does not help you locally

2. You don’t know the final result of dependencies

3. You don’t test what is exactly going to production

Git has solved efficient file transfer, but..

If you use git for deploying your code you still have to figure out how to configure your servers.

But it does not have to suck!

The is a pretty good solution for the problem and that is containers.

Now i hear some of you say, “Yes I know about docker” and that is correct, but docker did not invent containers, it was initially based on something called lxc which was released August 6, 2008, and there were even earlier similar projects. This means that docker is just a means to solve the problem, but you could easily use CoreOS rocket container format.

What all of those open source projects was missing was the tooling!

The tooling to easily

  1. package your app
  2. transfer your packaged app
  3. start your packaged app

So by using containers/docker you easily solve the three main problems!

1. Containers help you locally

2. You know the final result of dependencies

3. You test what is exactly going to production

There is a huge win with using containers and these are just some of them when talking about the file-transferring process of deployment.

-Kevin

Do you want to get started with containers?

Do you want to deploy a container?

Written by

I really like building stuff with React.js and Docker and also Meetups ❤

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store