Ok so what are we planning on achieving here?

Basically we want to have the ability to make changes, and test them on our local computer (or staging site) before pushing those changes to the live site.

I know in a real deployment we would have development, staging, live but for this tutorial I am only going to run through development and live. Why? Cause Im a lazy Hippy not a full blown developer.

So while we were going through the processes of settings things up I came across a this resource that might help you out as well:

• http://ottopress.com/2011/creating-a-wordpress-site-using-svn/

Before I start my ramblings I assume you know the basics of SVN, if not check out these resources before hand:

• http://codex.wordpress.org/Using_Subversion
• http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion
• http://svnbook.red-bean.com/

What you need:

• A sense of humor
• An Empty SVN Repository – (in this tutorial I will call this repository http://svn.example.com/site1)
• LAMP, XAMP or MAMP
• Some basic Terminal knowledge

1. Create your Work Environment

Create a folder ‘site1′ to hold the site (usually in your htdocs folder) navigate your way into it using terminal and Checkout a fresh, empty copy of your SVN repository:

svn co http://svn.example.com/site1 .

This should checkout a copy of the repository which should just a .svn folder and no other files.

2. Setup your Externals

This was the new and fun part, svn externals. we are going to include a copy of WordPress into a new folder called wp. In terminal navigate into your site1 folder and type in this command:

svn propedit svn:externals .

This will open up a text editor like vim, in here hit ‘i’ for insert. Then type :

wp http://core.svn.wordpress.org/tags/3.1/

Then hit ‘esc :wq’ and hit enter, you should see a message like “Set new value for property ‘svn:externals’ on ‘.’”

3. Update your Working Copy

With your new external in place type svn up to start downloading WordPress!

4. Setting up your wp-content folder

From the site1 folder in terminal type:

svn mkdir wp-content
svn mkdir wp-content/plugins
svn mkdir wp-content/uploads
svn mkdir wp-content/themes

Now instead of copying the akismet plugin and twentyten theme from wp/wp-content to wp-content we will add them as symbolic links (we will also do this with the index.php files which live in each folder, inside the wp-content folder in terminal type:

ln -s ../wp/wp-content/index.php index.php

Then in the themes folder:

ln -s ../../wp/wp-content/themes/index.php index.php
ln -s ../../wp/wp-content/themes/twentyten twentyten

Then in the plugins folder:

ln -s ../../wp/wp-content/plugins/index.php index.php
ln -s ../../wp/wp-content/plugins/akismet akismet

If you navigate into the site1 folder and do an svn st you will see all the symbolic links we just made have not been added to the repository yet. so we will have to go ahead and do that:

svn add wp-content/index.php
svn add wp-content/plugins/*
svn add wp-content/themes/*


5. Setting up your external Plugins

Thats great but we want a few other bits and pieces too, for example, I do a lot of work on the WP e-Commerce Plugin so I’d like to run the latest and greatest of that (or any other Plugin I run). Navigate to the plugins directory in terminal and type:

svn propedit svn:externals .

This will open up a text editor like vim, in here hit ‘i’ for insert. Then type :

wp-e-commerce http://svn.wp-plugins.org/wp-e-commerce/branches/3.8-development

Then hit ‘esc :wq’ and hit enter, you should see a message like “Set new value for property ‘svn:externals’ on ‘.’” Now all you need to do is type ‘svn up’ in terminal and wp-e-commerce plugin directory will be populated with the latest and greatest

6. Setup your .htaccess

So this part was awfully tricky for me, I’m no expert at .htaccess rules, so I just copied this part from the above resource. Essentially add a new .htaccess file to your site1 folder and add this to the file:

Options -Indexes
RedirectMatch 404 /.svn.*$
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/site1/wp/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /site1/wp/$1
RewriteRule ^(/)?$ wp/index.php [L]

Once you have done that, make sure you add it to the repository, in terminal:

svn add .htaccess


7. Setup your config file

With the .htaccess file rocking, you should now be able to navigate to site1 using a web browser and complete the normal WordPress Install which setups your DB and wp-config files. Once that has been done, I strongly suggest you

a. Change the permissions on your .htaccess file so WordPress can’t overwrite it.

b. Add these lines to your wp-config.php file so your install uses the correct wp-content folder:

define( 'WP_HOME', 'http://sites/site1' );
define('WP_CONTENT_DIR', dirname(__FILE__) . '/wp-content');
define('WP_CONTENT_URL', WP_HOME.'/wp-content');


8. Make your config file not part of the SVN repository

Ok, so having your wp-config file in the repository is a no-no. If someone accidentally got into your SVN Repo, or hacked in, then they will have your username, password and DB details.. which is a scary thought. So what we do here is make SVN ignore the wp-config.php file, so it doesn’t get added to the repo. In terminal navigate to site1 and type:

svn propedit svn:ignore .

This will open up a text editor like vim, in here hit ‘i’ for insert. Then type :

wp-config.php

Then hit ‘esc :wq’ and hit enter, you should see a message like “Set new value for property ‘svn:ignore’ on ‘.’”

9. Check in your new repo

With everything said and done, head over to site1 in terminal and type:

svn ci -m 'Checking in my new Website while learning how not to be a cowboy'

That’s that. We now have a repo for our new website, and can work on any computer without having to deal with the live site.. Things to consider:

• Data. What we have comitted had nothing to do with live data, so for instance if you are trying to do this with a currently active site I would import the DB and change the wp-config file once we have completed the steps above.
• Uploads Folder. now I haven’t heard any good / bad way to do this, and personally I log in to my live server every now and then and check in all my files in the uploads directory. That way I can download the latest DB and the files can associate after an svn up on my local working directory.

If you have any tips, advice, or found this post useful please leave a comment. I’m interested in extending this deployment strategy and learning how other people stopped being cowboys.

Note: If you are trying to setup propedits and are getting an error please try this in terminal:

vi ~/.bash_profile

This will open up a text editor like vim, in here hit ‘i’ for insert. Then type :

export EDITOR=vim
export SVN_EDITOR=vim

Then hit ‘esc :wq’ and hit enter, Quit terminal and try again, you should be able to get through successfully.

Till Next time,

Peace man!

• 500 Internal Server Error – 500 Internal Server Error
• Mangling strings for fun and profit « follow the white rabbit –
• New in WordPress 2.9: Post Thumbnail Images « Mark on WordPress –

• 500 Internal Server Error – 500 Internal Server Error
• Amazon.com: Test Driven Development: By Example (9780321146533): Kent Beck: Books –
• Installing/Updating WordPress with Subversion « WordPress Codex –

• Source Checkout – bp-e-commerce – Project Hosting on Google Code –
• BuddyPress.org → Docs → Make your plugin BuddyPress aware (v1.2) –
• Benchmarking WordPress SQL using FirePHP –

• WordPress › Custom Post Type UI « WordPress Plugins –
• Function Reference/register post type « WordPress Codex –
• Template Hierarchy « WordPress Codex –

• Theme Development Checklist « WordPress Codex –
• 5 tips for using AJAX in WordPress – WordPress Hardcore –
• 7 Simple and Useful Command-Line Tips | Nettuts+ –

Some of you may ask ‘Why is duplicating a WordPress site necessary?’

• Well I do it to test upgrades of wp-e-commerce, to make sure things don’t break after an upgrade and serves as a file backup if I ever need one in the future.
• They are also useful for backups
• It also comes in handy when developing new functionality specific to a site

A few things to note, if you are unfamiliar with SSH and terminal then I’d suggest you learning a little about that.. SSH is a more secure form if FTP, and it allows you to perform some functions that are either impossible or slow to do via FTP. Just Google ‘basic SSH commands’ and you should get some good info… I also just read a good ‘ 7 usefull terminal commands ‘ article on nettuts recently which I would highly recommend bookmarking.
I also assume you are running MAMP on your mac or XAMP on your PC and are familiar with using it.. If you are not and you are wanting to learn about being a web developer than you should Google them and download and install them.

Obtaining the files

1. Login to your server via SSH:

ssh Username@mywebsite.com

you will then be prompted to enter in your password.

2. Navigate to just outside your websites folder then use the zip command to zip up your files ( this might take awhile depending on the size of your site)

zip -r mybackup.zip mysite/

3. Move this file to a place accessible via a webbrowser (downloading it via SSH or FTP will take longer- I put it in the site the make sure to delete it once I’ve downloaded it)

mv mybackup.zip mysite/mybackup.zip

4. In a web browser navigate to http://mysite.com/mybackup.zip and download it.. Once it’s downloaded i usually move it into a folder outside of site so other people can’t download it instead of deleting it. Ie mv mysite/backup/mybackup.zip mybackup.zip

5. Now that we have the files it’s time to export the database, there’s a few ways of doing this.. I used to just use phpMyAdmin but there’s an even easier way if your already logged into SSH. All you need is the database host (usually localhost but can sometimes be different), username, password and database name.
In SSH type:

mysqldump --host=mysql.mysite.com --user=username --password=password --all-databases > mysite_db.sql

Once that’s done you should have a new sql file called mysite_db.sql repeat step 3 and 4 to download the file to your local computer.

Using the files

Cool now you should have two files on your computer that’s all we need to install a working version of your WordPress site locally.
Steps for installing are rather straight forward,

1. In your localhost environment unzip the mybackup.zip file so you have localhost/mybackup

2. In your localhost/mybackup/wp-config.php change your WP_USER, WP_PASS,WP_DB, and WP_HOST values to suit your localhost environment.

3. So now we have the files ready it’s time to make the database.. Login to your localhost phpMyAdmin and create a new database mysitedb then in the upper right corner select import and navigate to the files we downloaded (mysite_db.sql) and hit import

4. WordPress stores two options called ‘siteurl’ and ‘home’ which need to be changed otherwise if you try to login or view your site you will keep being sent to your real site online! This part confused the hell out of me the first time I tried it but was so aparent afterwards~ In your wp_options table search for the value siteurl and home then change them to the new location ie http://localhost/mybackup

Once this is done you should be ready to test your upgrades, work on modifications etc… Note sometimes you might get permissons errors on your wp-content folders, I usually resolve this issue by checking the sections in wp-admin>wordpress>miscellaneous section. You might also get the dreaded 500 Internal Server Error, in which case I usually delete the .htaccess rules or modify them slightly…

Well I hope you find this useful. I’m sure I’ll be reading this article again the next time I have to do a backup Good luck and happy coding!

Best
Jeff

• Setting Up Your Mac For Local Development Using Coda, WordPress & MAMP · Jay Robinson –
• Xdebug: Documentation –
• How To Create and Apply Image Filters in PHP –

• Command Line – OS X Daily –
• StudioPress › Support –
• 500 Internal Server Error – 500 Internal Server Error