WordPress
By Joe Gardiner Wednesday, 24th February 2010
What you will need:All the information from you vCluster Details page and Database Settings page. This includes: access server, public IP, database server, username, database name (the same as your username), and your database password. For quick reference during the WordPress install, you may find it useful to copy these details into a text file.
The newest version of WordPress, available to download from wordpress.org
A file extractor that is compatible with the .zip format. OSX and Windows handle this format natively.
An FTP program. You can use a program like FileZilla, or if you use Firefox web browser, there is an FTP add on available called Fire FTP. If your not sure which client to use have a look at this article.
A text editor. Notepad or Text Edit will both be fine.
A web browser. We like Firefox.
The official WordPress install guide can be found here.
Getting Started
Unzip your downloaded WordPress install to a folder on your desktop.
Open the newly unzipped WordPress folder, locate the file called "wp-config-sample.php", and rename it to "wp-config.php".
Open the newly named "wp-config.php" in you text editor and locate the MySQL Settings section.
After the 'DB_NAME' field, enter your username exactly as it appears in the Database Settings page, as this is the same as your database name.
After the 'DB_USER' field, enter your username.
After the 'DB_PASSWORD' field, enter your Database password. Note: This is different to your Access password, and can be changed in the Database Settings screen.
After the 'DB_HOST' field, enter the server name in the Database Settings screen. eg. xserve1.dc.fubra.net.
You can ignore the two remaining fields, ('DB_CHARSET' & 'DB_COLLATE').
Save and close the completed "wp-config.php".
Uploading
To upload WordPress files to the root directory of your vCluster follow the FTP upload guide.
To upload WordPress files to a sub-domain on your vCluster follow the vHosting guide.
Installing WP
Now we're now going to install WordPress using your web browser. Fire it up and navigate to your vCluster domain, with the edition of "/wp-admin/install.php" eg.customer.fubra.vc.catn.com/wp-admin/install.php
WordPress will take you through the installation procedure starting here:
Enter the relevant information and proceed. On the next screen, make a note or copy the admin password that has been generated, as you will require this to enter the WordPress Dashboard.
Click "Login", and enter the username as "admin" and the password you have copied from the previous screen.
Success! You will now have access to the WordPress Dashboard and have completed the install. Note: we and WordPress recommend changing your password to something you will remember immediately!
If you wish to install multiple sites using the new WordPress 3.0 multi-site feature, read this guide.
Posted in Guides, Installing an App |
7 Comments » 
I’m struggling to get pretty urls working, what should go into the .craccess file?
The .craccess file should contain exactly this:
RewriteEngine OnRewriteCond %{REQUEST_URI} !.(gif|jpe?g|png|css|js|ico)$
RewriteRule ^(.*)$ http://YOUR PRIVATE IP/$1 [P,L]
With your private IP, which can be found on the settings page of the control panel, replacing the text.
more information about the .craccess file is in this guide…
http://catn.com/blog/2010/03/02/multiple-domains-on-your-vcluster/
Yep – wp is working fine, my .craccess is as you detail, but this does not support pretty url’s in wordpress…
when you want to have urls like…
http://www.moneytoolkit.com/archives/123
instead of ….
http://www.moneytoolkit.com/?p=123
you normally have to update .htaccess to contian….
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
basically rewriting every url to the index.php, which then interprets the path correctly.
I cant get …
RewriteRule . /index.php [L]
to play nicely with…
RewriteRule ^(.*)$ http://10.x.y.z/$1 [P,L]
I dont know know about mod_rewrite
Hello Dan, yes the .craccess feature is currently not documented as well as it might be, but hopefully this explanation will help clear things up for you…
The .craccess file is just a “normal” .htaccess file running on the static content/proxy servers at tier 1. The main purpose of this file is to control the process of proxying dynamic content through to the application servers at tier 2. The tier 2 application servers then look for a file called “.htaccess”.
The reason for the two different file names is to allow granular control over both web server tiers, since both tiers would otherwise process the same overrides and things would just not work.
In the case of WordPress, the default .craccess file contents are adequate to get all dynamic requests to the application servers. Then you need to put the second set of rules into .htaccess as normal and the application servers will do the right thing.
So to recap… Put this in .craccess:
RewriteEngine On
RewriteCond %{REQUEST_URI} !.(gif|jpe?g|png|css|js|ico)$
RewriteRule ^(.*)$ http://YOUR PRIVATE IP/$1 [P,L]
… and this in .htaccess:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
… and things should work as expected!
The .craccess feature is now documented!
http://catn.com/blog/2010/03/22/craccess-and-htaccess/
Mark / Joe.
Awesome work – that makes total sense. Easy when you know how
Dan