I have just moved from Gandi to Linode. Getting more flexibility and saving some cash at the same time.
Nothing wrong with Gandi. I’ve really liked Gandi, and still use them for domain shopping and renewal, but having your own server is just so much more convenient than their (still awesome) simple hosting.
Merci for this time, Gandi folks!
I recently had some very nice experiences with gandi simple hosting (where the story tellers guild is located), which is in effect a “hosted VPS”, that is, a hosted solution, but with a private set of apache, mysql, APC and Varnish threads. Very cool indeed.
So I’m now moving this blog to the same platform.
10 minutes of work, and all appears to be working as expected.
- create the vhost(s) (with/without www.)
- add temp /etc/hosts entries while testing
- mysqldump the database (I took one of the cron-generated ones that was only an hour old)
- copy the files from the old DocumentRoot (put -r in sftp works in ubuntu for a recursive put, which was needed due to the amount of files)
- remove temporary /etc/hosts entry
- update DNS records to point to the new host
To finalize, I installed the varnish http purge plugin.
Looking forward to seeing the impact on performance in google webmaster tools.
In my last post about setting up WordPress on a LAMP, I omitted how to successfully enable permalinks, something you of course want to have on your blog.
Permalinks in WordPress is a way to have pretty URL:s to your posts to make it easy to link directly to them, and give them a human-readable format.
For it to work in a LAMP environment, you need to have mod_rewrite enabled in apache, and the tricky part when it comes to WordPress, is to enable mod_rewrite on the directory where your blog resides.
Most linux distros default to rather sane settings, and typically have something like this in them:
Options FollowSymLinks MultiViews
Allow from all
that means (if /var/www/html is your DocumentRoot), that WordPress’ way of using .htaccess to control the rewriting with mod_rewrite, will not work as intended (due to the AllowOverride None directive).
The fix is easy. Just add something like this to your apache config:
And you’ll be all set! (replace /var/www/html/wordpress above with the directory where you have wordpress installed. The same directory where wordpress created the .htaccess file when you enabled permalinks)
0. If you get permission denied on the shell commands, try prefixing them with “sudo ”
1. Log in as root in mysql:
lamp$ mysql -u root -p
2. Create a database and MySQL user dedicated to wordpress:
mysql> CREATE DATABASE blogdb CHARACTER SET utf8;
Query OK, 1 row affected (0.00 sec)
mysql> CREATE USER 'blogger'@'localhost' IDENTIFIED BY 'b1ogpw';
Query OK, 0 rows affected (0.05 sec)
mysql> GRANT ALL PRIVILEGES ON blogdb.* TO 'blogger'@'localhost';
Query OK, 0 rows affected (0.63 sec)
3. download and unpack wordpress into a directory served by apache:
lamp$ cd /var/www/html
lamp$ wget http://wordpress.org/latest.tar.gz
lamp$ tar zxf latest.tar.gz
lamp$ rm latest.tar.gz
lamp$ cd wordpress
4. configure wordpress with the database details and secret keys (edit all occurrences of the word “here”). Use the online generator to get good values for the secret keys:
lamp$ vi wp-config-sample.php
lamp$ mv wp-config-sample.php wp-config.php
5. run the wordpress installation script from a web browser. The URL will be like this:
6. Add the name for your blog, a user name (admin), password, your email address, and click the “Install WordPress” button att the bottom.
7. Done! Now log in, delete the sample post and sample page, and start customising your wordpress site.