![]() I’ll use the terminus command line tool to do this - terminus is Pantheon’s command line tool for the platform, they have documentation on getting setup here. Let’s dive into an example of how this could be setup.įirst, let’s spin up a Drupal 8 site on Pantheon to use. An example of this might be the “one click updates” that Pantheon’s dashboard provides - these commit directly to the repository. You can also automatically push changes back to GitHub whenever anything is committed directly in the Pantheon repo. With GitHub Actions, you can pretty easily connect your Pantheon repository, and any pushes to your GitHub repository can automatically be synced with your Pantheon repo. I was able to quickly get a lot setup, and that is what I look forward to sharing and exploring in this article. And, it appears to have a very decent developer community behind it, based upon the observed quality of community provided Actions, which can be integrated with your custom Action to easily provide functionality. Sure enough, after spending some time with it, it seems more than capable to do a *lot* of automation and continuous integration tasks, that I think could go far with a single or a fleet of sites. After a somewhat detailed read of the docs, it sounded robust enough to accomplish a good deal of automation and integration with Pantheon. Recently, I finally had a chance to take a closer look at it. I had heard about GitHub Actions, which is an automation service that GitHub provides, and have been curious for some time. There are lots of options out there when it comes to automation and “continuous integration”. That is, unless you want to deploy some automation. ![]() This makes sense if you want to take advantage of one or more of their offered features, but because it means you’d have two repositories - you will find yourself pushing to both GitHub and Pantheon repos, always having to make sure things are in sync. When you’re developing a Pantheon site, it’s likely you’d have the site source code in a GitHub repo. Whatever the case may be - Your team or yourself may already be used to the interface, tools, and workflow that GitHub provides. While the open source projects are plentiful, some opt to keep their git repo hidden with a private repository. It has a plethora of popular open source projects hosted on it, and is used by many businesses and individuals. In the world of git, stands out as a really awesome place to host your git repos. You can also deploy git branches as “Multidevs”, which are environments running any particular branch you want ( See here for the specifics) ![]() Any changes you push to the master branch are deployed to the “Dev” environment, and from there, you can deploy changes to “Test” and “Live”, “Live” typically being the environment which is connected to your domain(s), and this is done via automated git tagging. Each Pantheon site provides it’s own repository that connects directly with your application. The fact that it is git based enforces a best practice workflow. It’s deployment system is built entirely on git, the industry standard version control system. Pantheon is a fantastic WebOps platform for a Drupal or Wordpress site. In this story, we’ll go over a use case with WebOps platform Pantheon, and a Drupal 8 site. GitHub Actions allows for easy continuous deployment techniques.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |