Suggest a killer feature and win a DVD!
We work hard at Build a Module.com to make sure you have an amazing experience, but we also believe there's room for awesome new features. If there's an awesome feature you'd like to see, send it to us. In 1 month, we'll choose the best feature suggestion and award the winner with a free DVD of their choice!
More new Git videos
This week we begin by wrapping up our feature branch workflow, and then start diving into how to capture the other half of Drupal (i.e. the database) into version control. This is where things can get a little complicated, but getting our database information and configuration captured into version control as possible will help you roll back mistakes, review changes, and sleep at night, knowing you have a solid backup.
In this video, we prepare our feature branch to merge with the main develop branch by first merging in the changes in the develop branch. Then we deploy the feature branch back into the develop branch and clean up the feature branch. Whew!
In finishing up our feature branch, we take a step back and review what we learned in the process.
Since there's not a default place to put additional assets that aren't part of our code base, we talk about the best place(s) to put them.
If we decide to put our assets somewhere in our main Drupal directory, it's important to keep it safe from prying eyes. In this video we demonstrate how to use the .htaccess file to do just that.
FREE video tutorial of the week
Getting our code into version control is a great start, but that's just half the battle with Drupal, since so much information is captured in the database. In this video, we begin the process of exploring the best way to get database components into our Git repository.