Submitted by jenlampton on May 11, 2023 - 3:32pm
There are lots of different approaches to managing Backdrop CMS configuration files in Git, but this one is my favorite. It works great for projects with multiple developers, and it can also be easily adapted for multiple deployment environments, as on Pantheon.
This versioned staging directory strategy has been adapted from a recommendation from @populist and @davidstrauss based on how the
config directory is being managed for Drupal 8/9/10 on Pantheon.
Submitted by jenlampton on September 25, 2020 - 9:33am
When porting modules from Drupal 7 to Backdrop CMS, it's natural for people to download the Drupal project as usual, and then start to make changes to the code so it will work for Backdrop. When they have got a working Backdrop version of the module, they are often inclined to contribute it back to the Backdrop community -- which is great!
Submitted by jenlampton on January 21, 2017 - 2:24pm
Working with Git is great, but before you see the real benefits of using Git you'll need to have your project hooked up to a remote repository.
Most people enter the world of Git when they are brought on to a project with multiple developers. In this case, there is likely already an existing repo, and all you need to learn to do is pull the latest changes, and push your own.
Submitted by jenlampton on January 21, 2017 - 1:42pm
Tools like Git desktop and Acquia dev desktop allow people to use Git without understanding how it actually works. These tools are a fantastic on-ramp to the world of Git, but at some point I hope that everyone gets a chance to work with Git directly from the command line. This will complete your understanding of what happens when you push those buttons in the desktop applications, and make you better at using both! Here are some basics to get started.
Submitted by jenlampton on August 29, 2015 - 10:28pm
Submitted by jenlampton on August 9, 2013 - 9:41pm
I don't recommend trying to stay 100% on top of all updates for all of your modules all the time. However, when a security update becomes available for one of your modules, you should certainly make that update as soon as is reasonable. And while you're at it, that might be a good time to bring everything else up to date as well. Below is my recipe for keeping modules on my Drupal sites up to date, by using two of my favorite development tools, Git and Drush.