Basic Pantheon Workflow

Video loading...

  • 0:00
    Manage Drupal Sites with Pantheon Basic Pantheon Workflow Addison Berry
  • 0:09
    Let's take a look at the basic Pantheon workflow
  • 0:13
    and just get an overview of what tools Pantheon's actually providing here.
  • 0:18
    So in this lesson I'm just going to do a very, very brief overview
  • 0:23
    of the different workflow environments that you get and how you are expected
  • 0:27
    to use them. And then very briefly we'll talk about how you can actually access
  • 0:31
    your code so you can begin using the workflow.
  • 0:34
    So you get 3 environments
  • 0:38
    with Pantheon out of the box. So every time you create a site,
  • 0:41
    you have tabs for 3 different environments: dev, test, and live.
  • 0:46
    They are each a separate website, but it's the same site. So you're basically
  • 0:53
    making a complete copy of a site, and then it lives in parallel with the others.
  • 0:59
    And so you make changes to one, it doesn't necessarily reflect on the other.
  • 1:02
    And this is really handy because you're working with identical sites
  • 1:05
    rather than sort of close-ish. And they're all on the same infrastructure.
  • 1:11
    So you know that the server and all of those things, there's nothing funky
  • 1:15
    about the version of php or anything like that, that is different
  • 1:18
    between those environments. And Pantheon provides you with some nice UI tools
  • 1:23
    for reviewing and merging and deploying your code changes throughout these environments.
  • 1:30
    And the general idea here is that code goes up, and content comes down.
  • 1:35
    So let's talk about that in a little more detail.
  • 1:39
    This is the basic idea for a best practices workflow. This isn't just a Pantheon thing.
  • 1:46
    This is best practices and web development, and Pantheon's just providing
  • 1:49
    the environments and the tools for you to be able to use it very easily
  • 1:53
    without having to set it up yourself. So you would start doing your development
  • 1:59
    on a development version of the site. You begin building it. You're doing your thing.
  • 2:03
    And that's where all of the dirty things are happening and bugs probably are in there
  • 2:07
    that still need to be fixed and that kind of thing. So you have your development environment.
  • 2:10
    Now once you have things fixed and you would like to send those
  • 2:15
    up to your real live site, you first want to put those at a stopping point
  • 2:20
    where someone can test it, also sometimes referred to as QA or quality assurance site.
  • 2:26
    So what you want to do is you want to copy your site, and then you want to push
  • 2:31
    the code and the changes that you've been making in development into this test site.
  • 2:35
    And then people can bang on that site. They can find the bugs.
  • 2:39
    They can see what's going on in a stable environment that's not changing.
  • 2:42
    And this allows you to continue to do development on the other site.
  • 2:47
    A problem that you can often encounter if you don't have this intermediate step here
  • 2:53
    for testing is that if you test on your development server,
  • 2:56
    then that means all development has to stop while testing is going on
  • 3:00
    because you can't keep changing things for people to test.
  • 3:03
    So that's what nice about separating those into 2 different concerns
  • 3:07
    with 2 different sites. So you take your dev, you push it up to test,
  • 3:11
    people are testing it while developers are still working away.
  • 3:14
    And then once you're ready to go and you've approved what's happening on the test server,
  • 3:17
    then you would deploy that out to your live site.
  • 3:21
    And then you would start the process all over again.
  • 3:24
    So code always moves up. You're fixing things and you're just going to move it
  • 3:27
    through that system. Now for content, what you want to do
  • 3:31
    is you want to make sure that your dev and your test environments
  • 3:34
    are accurate and up to date with what's going on.
  • 3:37
    And so you can bring content down from your live site
  • 3:41
    because people are still doing stuff on the live site. Right?
  • 3:44
    It's out there. People are adding content and doing things to it.
  • 3:47
    So what you want to do is bring that content back down
  • 3:51
    to your test and your dev environments so that you make sure that you're matching
  • 3:54
    the live site as closely as possible while you're doing your work.
  • 3:58
    And Pantheon provides nice tools that let you push your code from dev to test
  • 4:03
    and from test to live, and then they also have something that will allow you
  • 4:06
    to bring your content down so you don't have to do any of that manually.
  • 4:10
    You can let Pantheon handle the inner workings of making that happen for you.
  • 4:16
    Now when it comes to connecting to your code
  • 4:20
    so you can begin working on your workflow, when you create a new site
  • 4:24
    you have 2 ways of accessing the code. You can have SFTP, which is the default setting.
  • 4:30
    So that would be a secure file transfer protocol where you would log in
  • 4:35
    to the server using an FTP client and then you can edit the files
  • 4:39
    and replace files and move them around and that kind of a thing.
  • 4:42
    And then there's also Git, which is sort of the standard way for keeping track
  • 4:46
    of your code. Using version control is an amazing tool, so much better than SFTP
  • 4:52
    in a lot of ways. So if you're at all familiar with Git or if it's something
  • 4:58
    that you are curious about, I would highly recommend that you explore using Git.
  • 5:01
    For Git, one thing to keep in mind is you have to have SSH Keys.
  • 5:05
    And we have another lesson that talks about how you would enter your SSH Keys
  • 5:10
    into Pantheon so that Pantheon will recognize your Git connections
  • 5:14
    when you need to start working with the code. But you can choose either method
  • 5:19
    to access the code that you would then use the UI to push those changes through.
  • 5:23
    And you can get that connection information in your site dashboard.
  • 5:28
    So this was a short video
  • 5:31
    just to give you an overall sense of what Pantheon's providing for you
  • 5:34
    in terms of workflow environments and what the expectation is
  • 5:39
    for how you are supposed to use dev, test, and live.
  • 5:42
    And then we talked real briefly about how to access your code
  • 5:45
    so you can begin using this workflow and get your code moving from dev to test to live.

Basic Pantheon Workflow

Loading...

With your site created or imported into Pantheon, it's time to begin getting some work done on it. In this presentation we'll provide an overview of how Pantheon is set up to support your development workflow, from making changes to your code base on dev to getting your site launched on live. We'll discuss the three environments that Pantheon provides—Dev, Test, and Live—and review how to get access to your code.

Sponsored by Pantheon

Downloads: 
Log in or sign up to download companion files.
Additional resources: