github-migration
/
vagrant-wordpress
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A Vagrant base project for building Wordpress themes
10 Commits 1 Branch 0 Tags 163 KiB
HTML 72.7%
Ruby 27.1%
Perl 0.2%
Go to file
Eric Teubert c393a557a0 modernizations 
- always fetch lates WordPress version
- skip checksum
- add rake task :setup to install my custom shell
 		2011-12-17 12:21:49 +01:00
cookbooks modernizations 2011-12-17 12:21:49 +01:00
plugins mount 3 most common used folders: themes, plugins, wordpress 2011-12-06 18:57:36 +01:00
themes mount 3 most common used folders: themes, plugins, wordpress 2011-12-06 18:57:36 +01:00
wordpress mount 3 most common used folders: themes, plugins, wordpress 2011-12-06 18:57:36 +01:00
.gitignore extend .gitignore 2011-12-06 19:17:43 +01:00
Gemfile Initial commit 2011-06-12 14:15:48 -07:00
Gemfile.lock Initial commit 2011-06-12 14:15:48 -07:00
Rakefile modernizations 2011-12-17 12:21:49 +01:00
Readme.md added some more info about selecting a new theme in Wordpress 2011-09-17 15:00:24 +01:00
Vagrantfile modernizations 2011-12-17 12:21:49 +01:00

Readme.md

Vagrant Wordpress Theming

This is a Vagrant setup for creating Wordpress themes. Uses Chef Solo recipes for provisioning. The recipes are copied from my fork of those by Opscode, which allows for their use with Chef Solo and for a blank MySQL root password.

NEVER WORRY ABOUT SETTING UP MYSQL AND PHP ON YOUR MAC EVER AGAIN!

Requirements

To get started

$ git clone git://github.com/paulcarvill/vagrant-wordpress.git
$ cd vagrant-wordpress
$ vagrant up
$ open http://localhost:8080

You'll need to install Wordpress (i.e. set up an admin user, name the Wordpress blog etc.). Then copy a base theme (like the totally stripped-down Starkers) into the theme directory, select Appearance > Themes in the Wordpress dashboard, choose the new theme and get to work!

Your Ubuntu/PHP/MySQL box exists as a virtual machine. The website running on the virtual machine is pointing back at the theme directory on your local machine. So you can do your work, keep it in version control, and destroy the virtual machine once you're finished using:

$ vagrant destroy