Archived video

This video is archived and won't be updated. We're keeping it online for now as a courtesy.

Alternate resources: 

Git, Deployment and Beanstalk

Video loading...

  • 0:01
    [robotic voice] Drupalize.Me. [ - Learn Drupal]
  • 0:04
  • 0:06
    [Git, Deployment and - Deploying Your Code Without a Terminal]
  • 0:10
    [Chapter 1 with Kyle Hofmeyer]
  • 0:12
    In this lesson we're going to cover what I like to call the newbies
  • 0:17
    or maybe the novice users or maybe the "I want to play with the big boys
  • 0:21
    "but I don't want to use the big boys' toys" or big girls, if you will.
  • 0:25
    So what is this? It's code deployment with
  • 0:29
    Deploy your code and never open a terminal.
  • 0:34
    What does it mean to deploy your code?
  • 0:36
    I looked up deploy and I was going to put a fantastic definition of it right here,
  • 0:39
    but instead I made one up.
  • 0:41
    Move your code from environments such as local to production.
  • 0:45
    Well, I do this already.
  • 0:46
    I open up my FTP program, I drag the folder
  • 0:49
    that has my website that I've been working on locally,
  • 0:52
    and I drag it to my server, and it uploads.
  • 0:54
    And there you go, I deployed my site.
  • 0:58
    Sure, you deployed your site, but what you didn't do
  • 1:01
    was your site was not in version control.
  • 1:05
    Version control is a must.
  • 1:07
    It's not just for developers.
  • 1:09
    Again, it's not just for developers.
  • 1:11
    I can easily say that because I am not a developer.
  • 1:14
    But what I do is I work on websites, and I do a lot of stuff and I do it in version control.
  • 1:19
    Why do I do that?
  • 1:21
    I was told to and because I wanted to learn how to do it
  • 1:23
    and I found out why it's a good idea to put stuff into version control.
  • 1:26
    Why is it?
  • 1:28
    First of all, this gives you a backup of everything that you're working on.
  • 1:31
    You can now be part of the team.
  • 1:33
    Teams work in version control systems, and everybody is working on different things,
  • 1:36
    and those things come together and they're brought together,
  • 1:38
    and the version control system handles all of this.
  • 1:41
    And that's why version control is helpful.
  • 1:43
    Also you can fix your mistakes.
  • 1:45
    So if you realize down the line that yesterday that was working, today it's not,
  • 1:49
    what can I do?
  • 1:50
    Version control can allow you to roll back to yesterday if you want.
  • 1:53
    Also, version control is just a good idea.
  • 1:58
    Git. Git is a type of version control.
  • 2:00
    It's a type of version control we're going to be discussing in this lesson.
  • 2:03
    It's also the type of version control that Drupal uses,
  • 2:06
    hence the reason why we're talking about it.
  • 2:08
    Git: You don't have to be a rocket scientist to use it,
  • 2:11
    although being a rocket scientist might help you use terminal
  • 2:14
    and do some crazy stuff and put some cool commands in there
  • 2:16
    that run all these things that are going on inside of Git.
  • 2:19
    But guess what?
  • 2:20
    You don't need to do that to be able to take advantage of Git and version control.
  • 2:24
    Also there's a GUI for that.
  • 2:26
    Sure, Git does have many, many, many GUIs out there for Windows or for Mac.
  • 2:31
    In this lesson we're going to be using Tower, a Git GUI, on the Mac operating system.
  • 2:36
    And like I said, Git--it's what's Drupal uses, it's what the contributor modules use,
  • 2:40
    and it's what core uses.
  • 2:42
    Finally, like I mentioned, it's excellent for collaboration,
  • 2:45
    and Git makes bringing people's codes and figuring out conflicts together a lot easier.
  • 2:52
  • 2:53
    Never manually FTP or SFTP your site again. It's fantastic.
  • 2:58
    You'll never have to do that again.
  • 3:00
    You only update what needs updating.
  • 3:03
    It's not a matter of what we used to do, which was just probably grabbing all the files
  • 3:07
    to our site and uploading them in or maybe even just a folder of files.
  • 3:10
    You can work locally, and then what you'll do is you'll use deployment,
  • 3:14
    and that will basically take what you've done and get it to your production server.
  • 3:18
    And finally, we're going to be working with the
  • 3:22
    This makes this all super easy with no terminal required.
  • 3:25
    We're going to show you how you can have a repository,
  • 3:29
    make some changes locally, commit those into the repository,
  • 3:32
    merge that into your master branch,
  • 3:37
    and then what we're going to do is we're going to have that deployed to your production server.
  • 3:40
    And you can do all of this--all of this--with just a GUI and a web interface.
  • 3:44
    [ - Learn Drupal]

Git, Deployment and Beanstalk


We introduce code deployment without a terminal using

Deployment means moving your code from environments such as local to production – with version control, which allows for backups, fixing mistakes, and collaborative environments.

Git is the type of version control used in Drupal, and we'll discuss Git in this lesson.

Additional resources: