Spaces

source/_posts/2013-11-19-dont-bootstrap-drupal-use-drush.md

@@ -2,9 +2,9 @@
 title: Don't Bootstrap Drupal, Use Drush
 nav: blog
 tags:
-    - drush
-    - drupal-planet
-    - php
+  - drush
+  - drupal-planet
+  - php
 ---
 There are times when doing Drupal development when you need to run a custom PHP script, maybe moving data from one field to another, that doesn't warrant the time and effort to create a custom module. In this scenario, it would be quicker to write a .php script and bootstrap Drupal to gain access to functions like `node_load()` and `db_query()`.
 
@@ -25,7 +25,7 @@ $node = node_load(1);
 
 The script would need be placed in the root of your Drupal directory, and you would then have had to open a browser window and visit http://example.com/foo.php to execute it. This is where the "drush php-script" command (or "drush scr" for short) is useful, and can be used to execute the script from the command line.
 
-        $ drush scr foo.php
+    $ drush scr foo.php
 
 It also means that I no longer need to manually bootstrap Drupal, so my script is much cleaner.
 
@@ -38,10 +38,10 @@ $node = node_load(1);
 
 I prefer to keep these scripts outside of my Drupal directory in a separate "scripts" directory (with Drupal in a "drupal" directory on the same level). This makes it easier to update Drupal as I don't need to worry about accidentally deleting the additional files. From within the drupal directory, I can now run the following command to go up one level, into the scripts directory and then execute the script. Note that you do not need to include the file extension.
 
-        $ drush scr ../scripts/foo
+    $ drush scr ../scripts/foo
 
 Or, if you're using [Drush aliases](http://deeson-online.co.uk/labs/drupal-drush-aliases-and-how-use-them "Drupal, Drush aliases, and how to use them"):
 
-        $ drush @mysite.local scr foo
+    $ drush @mysite.local scr foo
 
-If you commonly use the same scripts for different projects, you could also store these within a separate Git repository and checkout the scripts directory using a [Git submodule](http://git-scm.com/book/en/Git-Tools-Submodules "Git Submodules"). 
+If you commonly use the same scripts for different projects, you could also store these within a separate Git repository and checkout the scripts directory using a [Git submodule](http://git-scm.com/book/en/Git-Tools-Submodules "Git Submodules").