Managing a WordPress 2.6 installation with Subversion

Managing a WordPress 2.6 installation with SubversionSam Bauers - Automattic

In this presentation...

- Overview of version control and Subversion

- Anatomy changes in WordPress 2.6

- Creating a “clean” WordPress install

- Creating a Subversion project that incorporates WordPress

- Early adopter pitfalls

WordPress 2.6 + Subversion

Version control



Repository

Version control


RepositoryWorking

copy

Version control

Version control


RepositoryWorking

copy

Version control


RepositoryWorking

copyWorking

copy

Version control


Version control


Revision 14

Sam

Tony

Version control


Revision 14

Sam

Tony

Revision 14

Version control


Revision 14

Sam

Tony

Revision 14

Revision 14

Version control


Revision 14 Revision 15

Sam

Tony

Revision 14

Revision 15

Version control


Revision 14 Revision 15

Sam

Tony

Revision 15

Revision 15

Version control


Revision 14 Revision 15 Revision 16

Sam

Tony

Revision 15

Revision 16

Version control


Revision 14 Revision 15 Revision 16 Revision 17

Sam

Tony

Revision 15

Revision 17

Version control



Sam

Tony

Revision 17

Revision 17

Version control



Sam

Tony

Revision 18

Revision 17

Revision 18

Version control



Sam

Tony

Revision 18

Revision 18

Revision 18

Version control


Version control


You

Server

Version control


Revision 1

You

Server

Revision 1

Version control


Revision 1

You

Server

Revision 1

Revision 1

Version control



You

Server

Revision 5

Revision 5

Revision 5

Version control



You

Server

Revision 5

Revision 3

Revision 5

Version control

- Revision history

- Annotated

- Time stamped

- User accountable


Version control

- Code development

- Multiple developers

- Structured workflow

- Conflict resolution when updating and merging

- Potentially remote

- Branching and tagging

- Maintain experimental and stable versions

- Tag releases as perpetual snapshots


Version control

- Server deployment

- Single command to deploy

- Mostly automatic conflict resolution

- Version rollback

- Version synchronisation across multiple servers

- Potentially scriptable


Subversion


Subversion

- Centralised version control system

- Works over http and https via Apache webserver

- Used by Automattic

- WordPress and bbPress

- Plugin repositories

- WordPress.com

- Server config files

- Design documents - Photoshop, Illustrator, etc.


Subversion

http://svnbook.red-bean.com


WordPress 2.6 anatomy




A



B



AB

“Clean” WordPress




Assumptions

- Installing in root directory of the domain

- Domain is example.com

- Path to root directory of website is /var/www/root/

- Access to rewrite rules for permalinks



> cd /var/www/root/



> cd /var/www/root/

> svn checkout http://svn.automattic.com/wordpress/branches/2.6 wordpress



Now install WordPress at

http://example.com/wordpress

Don’t change any settings yet!



> cd /var/www/root/




> cd /var/www/root/


> mv wordpress/wp-config.php wp-config.php



> cd /var/www/root/





> cd /var/www/root/



> mkdir wordpress-content



> cd /var/www/root/




> cd wordpress-content



> cd /var/www/root/





> mkdir plugins



> cd /var/www/root/





> mkdir plugins

> cd plugins



> cd /var/www/root/





> mkdir plugins

> cd plugins

> ln -s ../../wordpress/wp-content/plugins/akismet



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..

> mkdir themes



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..

> mkdir themes

> cd themes



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..

> mkdir themes

> cd themes

> ln -s ../../wordpress/wp-content/themes/default



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..

> mkdir themes

> cd themes


> cd ..



> cd /var/www/root/





> mkdir plugins

> cd plugins


> cd ..

> mkdir themes

> cd themes


> cd ..

> mkdir uploads

WordPress inside aSubversion project


WordPress inside a Subversion project

- Store your own code inside a subversion project

- Include WordPress as an “external” repository

- Ignore certain directories




> svn propedit --editor-cmd nano svn:externals .



GNU nano 2.0.1 File: svn-prop.tmp Modified

^G Get Help ^O WriteOut ^R Read File ^Y Prev Page ^K Cut Text ^C Cur Pos

^X Exit ^J Justify ^W Where Is ^V Next Page ^U UnCut Text ^T To Spell




wordpress http://svn.automattic.com/wordpress/branches/2.6






> svn propedit --editor-cmd nano svn:ignore wordpress-content




uploads






uploads

cache







> svn status





> svn status

M .

M wordpress-content

Performing status on external item at 'wordpress'





> svn status

M .

M wordpress-content


> svn commit -m “Add WordPress external and ignore certain content directories”





> svn status

M .

M wordpress-content


> svn commit -m “Add WordPress external and ignore certain content directories”

> svn update



> svn propedit --editor-cmd nano svn:externals wordpress-content/plugins




wp-stats http://svn.wp-plugins.org/wp-stats/tags/2.31






> svn update




> svn update

Fetching external item into 'wordpress-content/plugins/wp-stats'

Early adopter pitfalls



- Plugins

- Many attempt to include wp-config.php

- They need to include wp-load.php

- They may need to manually set the path to it

- PLUGINDIR is deprecated, use WP_PLUGIN_DIR

- Use WP_PLUGIN_URL to construct URLs

- Beware AJAX plugins - they must use the API



- Themes

- Use get_theme_root()

- Use get_theme_root_uri()



- Directory and file permissions

- Stop WordPress from editing .htaccess

- Remember to open up uploads


Happy subverting!


Managing a WordPress 2.6 installation with Subversion

Documents

Transcript of Managing a WordPress 2.6 installation with Subversion