Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Update to use new wordpress plugins/themes method.

  • Loading branch information...
commit 43322e6bd3a9467135bbcaba8745bfe9f794dedd 1 parent 45fd0d0
Lew Goettner authored

Showing 3 changed files with 43 additions and 13 deletions. Show diff stats Hide diff stats

  1. +9 6 Cheffile.lock
  2. +20 5 README.md
  3. +14 2 Vagrantfile
15 Cheffile.lock
@@ -3,10 +3,11 @@ SITE
3 3 specs:
4 4 apache2 (1.1.8)
5 5 apt (1.4.2)
6   - build-essential (1.0.0)
  6 + build-essential (1.0.2)
7 7 chef_handler (1.0.6)
8   - mysql (1.2.4)
  8 + mysql (1.2.6)
9 9 openssl (>= 0.0.0)
  10 + windows (>= 0.0.0)
10 11 openssl (1.0.0)
11 12 php (1.0.2)
12 13 build-essential (>= 0.0.0)
@@ -15,29 +16,31 @@ SITE
15 16 subversion (1.0.0)
16 17 apache2 (>= 0.0.0)
17 18 windows (>= 0.0.0)
18   - xml (1.0.2)
  19 + xml (1.0.4)
19 20
20 21 GIT
21 22 remote: https://github.com/lewg/chef-wordpress
22 23 ref: all-the-things
23   - sha: 3b513977c05b3db84932d882fc6879f713ff1c78
  24 + sha: 215ea9b0e79f43f32c6fffa97955528876738d5c
24 25 specs:
25 26 wordpress (0.8.8)
26 27 apache2 (>= 0.99.4)
27 28 mysql (>= 1.0.5)
28 29 openssl (>= 0.0.0)
29 30 php (>= 0.0.0)
  31 + subversion (>= 0.0.0)
30 32
31 33 GIT
32 34 remote: https://github.com/opscode-cookbooks/windows
33 35 ref: master
34   - sha: 924e460f33620c7da5f72e27ef144da75d943437
  36 + sha: 2474490602c570156b79cd2c003d1412dff4d576
35 37 specs:
36   - windows (1.2.12)
  38 + windows (1.3.0)
37 39 chef_handler (>= 0.0.0)
38 40
39 41 DEPENDENCIES
40 42 apt (>= 0)
  43 + build-essential (>= 0)
41 44 subversion (>= 0)
42 45 windows (>= 0)
43 46 wordpress (>= 0)
25 README.md
Source Rendered
@@ -55,7 +55,7 @@ I've added a host-only IP of 192.168.33.20. If you plan to run multiple boxes at
55 55
56 56 I've put commented lines in there for mapping folders into both the plugins and themes folders. Uncomment, adjust to your local paths, `vagrant reload` and your local folders are now being run by the WordPress install in your VM. Look for these lines:
57 57
58   - # Example Theme Mount
  58 + # Example Theme Mount
59 59 # config.vm.share_folder "my-theme", "/var/www/wordress/wp-content/themes/my-theme"
60 60
61 61 # Example Plugin
@@ -64,11 +64,26 @@ I've put commented lines in there for mapping folders into both the plugins and
64 64
65 65 ### WordPress.org Plugin and Themes
66 66
67   -You can specify a list of plugins and/or themes to automatically when the VM comes up. Debug Bar is in there as a default (you are using this for development, right?) but you can add and remove to match your setup. Plugins can be specified by their relative path on WordPress.org (http://http://wordpress.org/extend/plugins/**[PATH]**/). For readability you can also put in the name if it happens to match the URL after it's lowercased, and had spaces swapped for dashes (e.g. 'Debug Bar' becomes 'debug-bar'). A lot of WordPress plugins and themes adhere to that rule. The relevant lines in `Vagrantfile`:
  67 +You can specify a list of plugins to automatically when the VM comes up. Debug Bar is in there as a default (you are using this for development, right?) but you can add and remove to match your setup. By default, just given a name, the defintion will attempt to guess the path to the plugin (on plugins.trac.wordpress.org) by replacing all the spaces with dashes, and removing some punctutation. Additionally, it will pull the latest version of the plugin based off the information provided by the plugin's readme.txt file. However, both the path and tag can be overridden ('trunk' being a special case, and choosing the trunk of the repository over a tag) The relevant lines in `Vagrantfile`:
  68 +
  69 + # Include the list of plugins you'd like installed
  70 + "org_plugins" => {
  71 + 'Debug Bar' => {},
  72 + #'Bit.ly Service' => {
  73 + # 'path' => 'bitly-service',
  74 + # 'tag' => 'trunk'
  75 + #}
  76 + },
  77 +
  78 +Like the plugin defintion and recipe above, there is also the ability to install themes from the wordpress.org theme repository. The syntax is the same as above, and by default the `Vagrantfile` has the two examples commented out:
68 79
69   - # Include the list of plugins you'd like installed
70   - "org_plugins" => [ 'Debug Bar' ],
71 80 # Include the list of themes you'd like installed
72   - 'org_themes' => [],
  81 + 'org_themes' => {
  82 + #'Toolbox' => {},
  83 + #'Pagelines' => {
  84 + # 'path' => 'pagelines',
  85 + # 'tag' => '1.1.3'
  86 + #}
  87 + },
73 88
74 89 Unlike the mount points, you don't have to restart the VM if you add plugins or themes, just trigger a chef run with `vagrant provision`
16 Vagrantfile
@@ -94,9 +94,21 @@ Vagrant::Config.run do |config|
94 94 },
95 95 "wordpress" => {
96 96 # Include the list of plugins you'd like installed
97   - "org_plugins" => [ 'Debug Bar' ],
  97 + "org_plugins" => {
  98 + 'Debug Bar' => {},
  99 + #'Bit.ly Service' => {
  100 + # 'path' => 'bitly-service',
  101 + # 'tag' => 'trunk'
  102 + #}
  103 + },
98 104 # Include the list of themes you'd like installed
99   - 'org_themes' => [],
  105 + 'org_themes' => {
  106 + #'Toolbox' => {},
  107 + #'Pagelines' => {
  108 + # 'path' => 'pagelines',
  109 + # 'tag' => '1.1.3'
  110 + #}
  111 + },
100 112 'version' => 'latest'
101 113 }
102 114 }

0 comments on commit 43322e6

Please sign in to comment.
Something went wrong with that request. Please try again.