Movin' On Out


I have finally re-established my relationship with Slicehost (oh, you didn't know I left. Well, it had nothing do with them; it was a personal decision on my part to leave temporarily). And now that I feel that this time I will be sticking with Slicehost more permanently, it is time to do some housekeeping.

One item on the agenda is to move this blog from to Slicehost.

There may be some intermittent downtime, but hopefully I can get this all up and running by the end of this week.

As I understand it -- will remain, but be stale (with this as the last post). That is, of course, unless I delete the old blog. will be transferred to the new host where you will see all of my previous posts, including this one, and all new posts.

We'll see how it goes!

See you on the flip-side.

Installing a LAMP Server, with Wordpress, on Slicehost (and maybe elsewhere)

[UPDATE: April 19, 2009: I added a follow-up post to this article with some more tidbits]

[Disclaimer: I am not responsible for any mishaps that may occur by following these steps or advice because you follow them out of your own free will.] -- I figure I better put that up-front. :-)

Someone wrote me an email today asking me how to get a LAMP server up and running on a Slicehost VPS ( Slicehost land, your VPS is called a "slice").

During the time when I was setting up my slice, I made a little personal document on how to set up a LAMP server with Wordpress (I used Ubuntu Hardy as my base Linux installation).

While this is by no means anything official or 100% complete, I figure when I need to set up a LAMP server again, it will serve as a great starting point for me.

Like I insinuated in my disclaimer, I cannot guarantee the accuracy  or the 100% "foolproof"-ness of these steps. I am by no means an expert at this stuff, but, hey, they worked for me.

Below are the contents of that document in its raw form. Feel free to ask any questions, although I cannot guarantee I will know the answer. Feel free to correct any mistakes in comments, although I cannot guarantee I will fix them.

Ubuntu Linux (Server): Setup @ Slicehost

Basic Commands and Instructions

  • sudo aptitude install <package1> [package2]
  • sudo aptitude purge|remove <package>
  • whereis <program> (to find out where something is located)
  • root shell: sudo –s (get out of the root shell by ctrl+d)
  • ps aux (to find out processes running) (ps aux | grep <process name> to narrow --- e.g., ps aux | grep httpd)
  • apache2ctl configtest (to make sure your Apache configurations are ok)
  • Apache logs are at /var/log/apache2 (Must be in a sudo shell -- see above)
  • sites-enabled is a symlink; make vhost changes to sites in /etc/apache2/sites-available
  • Don’t worry about .htaccess and httpd.conf files. Use vhost config files instead.


  1. Get bare bones install
  2. Log on as root via ssh ( ssh root @ <ip address> )
  3. Use provided password and immediately change it via passwd.
  4. Change time zone
    • sudo ln –sf /usr/share/zoneinfo/US/Pacific /etc/localtime (replace US/Pacific with what your timezone is)
  5. Follow these instructions for security
  6. Backup the private (and public if you want, but especially private) key from your local machine! (preferably in a couple different places)
  7. Continue with these security instructions (add \u@\ before \h\ to add user name in front of hostname in PS1)
  8. A good package to install would be unzip for downloads (only tar is available at this point): sudo aptitude install unzip ( )

Setup Domain via DNS Manager

  1. Log into the slice manager:
  2. To configure the DNS records for your domain, go here:
    • Make sure you have set the nameservers properly on your registrar (e.g.

Setup Domain Email via DNS Manager

  1. I use Google Apps for email. The next steps are specific to that. If you don’t use Google Apps, just make sure you set the MX records properly in the Slicehost DNS manager, otherwise you may be without email if you have completed the “Setup Domain via DNS Manager” step.
  2. If you haven’t done so already, set up Google Apps for your domain (
    • For verification, you can use the HTML method since you can control your website
  3. Set up the MX records like described here:


  1. Start here: (making sure you use your own server name and user names)
  2. Read to understand enabling/disabling sites and modules
  3. Follow these instructions:, and at least change the Timeout and KeepAliveTimeout to something much lower.
  4. Follow these instructions:
  5. Read these articles about virtual hosts before setting things up:,
  6. Read this article to understand how you are going to layout your directory structure for the domains you are going to host:
  7. Secure virtual host permissions and create skeleton virtual host directory:
    • For all new domains, just follow the following command:
      • cp –a /home/<user>/public_html/skeleton /home/<user>/public_html/<new domain>
  8. Create your first virtual host: (remember to change, to your own domains in the examples AND 'demo' to your username) (note: search and replace in nano is “ctrl-\”)
    • Remember that if they navigate to the IP Address, they will most likely get the “It Works!” message for the default Apache site. You can change this.
    • Change DirectoryIndex to “index.php index.html” if you are going to be using WordPress
  9. Change and add settings in your domain virtual hosts file:
    • Make sure you set some directory options – one I would for sure do is turn off directory browsing


  1. Follow the instructions here: Only do the MySQL part and make sure you do not put the Ruby option in the install string (unless you want Ruby of course)
  2. Follow post setup instructions here: to secure your initial mySQL accounts
  3. After I am done, I like to clear the mySQL console history. Exit mySQL and at the command prompt do 'rm ~/.mysql_history'
  4. Setup DNSUtils (for dig especially): sudo aptitude install dnsutils 

Set Up Sending Mail From Slice

  1. You need to change “exim” settings on server to send email from Wordpress
  2. For Google Apps, see this thread: Follow the instructions all the way down to Run # chown. I didn’t have to do this.
    • Also, accept all defaults for questions after the DNS-queries minimal question. There are more than the thread instructions let on.
  3. See this thread for more general info: (don’t need sendmail after all, exim is already installed so try that first, see page 2 of thread for meat)
  4. Now for multiple email addresses (when you have more than one blog, for example, each representing a different domain), you will need to follow some different steps. This might be a good place to start:


  1. Load mod_rewrite for Apache
    • Sudo a2enmod rewrite
    • Sudo /etc/init.d/apache2 reload
  2. Follow instructions here: (especially Detailed instructions)
    • DB Name: wordpress (or whatever)
    • DB UserName for wordpress: wordpress (or whatever)
    • Append table names if (1) you want more security (2) going to have more than one Wordpress blog using the same database
  3. Probably don’t want to put on google and technorati until you are done with the blog design
  4. Make sure to change admin password after first log in
  5. Change the “admin” user in MySQL to something else:
    • Mysql> use wordpress;
    • Mysql> UPDATE <wpTableName>users SET user_login=’admin’, user_login=’<new admin name>’;
  6. NOTE: Many instructions say to add things to “.htaccess” or “httpd.conf”. Since you have root access, don’t worry about these files. Make your configuration changes to the vhost file (or maybe, sometimes, the master apache2.conf file).
  7. Add Rewrite Log to vhost file
  8. Turn off directory in “public” browsing in the vhost
    • <Directory /home/<user>/public_html/<domain>/public>
      • Options –Indexes
    • </Directory>
  9. Put wp-config.php database and key info into another file and put that new file in /home/<user> (outside the public_html). Then put an include to hat file in wp-config.php. This is for security ( )
  10. Log into the Wordpress admin panel (http://<domain>/wp-admin/) and go to Settings/Permalinks. Set the permalinks to something like “Day and name” and click on Save Changes
    • Then, assuming you don’t have an .htaccess file, go to the bottom of the page and copy the code in the text area and paste in your vhost file (within the <Directory></Directory> for the top level directory (usually /home/<user>/public_html/<domain>/public)
  11. Do some security around the wp-content, wp-includes and wp-admin directories.
    • Only allow access to images and javascript to wp-includes and wp-content
      • <Directory /home/<user>/public_html/<domain>/public/wp-includes>
        • Options –Indexes
        • AllowOverride None
        • Order Allow, Deny
        • Deny from all
        • <Files ~ “.(css|jpg|jpeg|png|gif|js)$”>
          • Allow from all
        • </Files>
      • </Directory>
      • ….and do the same for wp-content
    • Either restrict access to wp-admin by adding a password layer or by IP address
    • You might also want to do the same as you did for wp-asmin for wp-login.php at the file level since going to http://<domain>/wp-admin redirects there (see:
      • <Files /home/<user>/public_html/<domain>/public/wp-login.php>
        • …..
      • </Files>
  12. Install login plug-in @ Copy the download link and use ‘wget’ to get it from the command line (instead of FTP)
  13. Activate the akismet plugin in the admin panel.
    • You need a account so you can get an API key. This key is found in Settings/Your Profile
  14. Install WP-Super-Cache plug-in



This is a MySQL front-end that is more user friendly than the default mySQL client

  1. sudo aptitude install phpMyAdmin
    • IMPORTANT: Make sure you press the space bar when selecting the web server you are using
  2. Go to /etc/apache2/conf.d/ and edit phpmyadmin.conf
    • Change Alias from phpMyAdmin to something more obscure for security purposes
  3. Change the /etc/phpmyadmin/ file to support https:
  4. Then go to

State of the Me - Quick Hits

It has been a while since I have given a progress report of where things stand for me professionally. Back when I worked for Intel, I was mandated to give monthly status report. I am feeling nostalgic today.

Here is  quick bulleted list.

  • I am still consulting, but, unless I am told otherwise, my current work is ending fairly soon here (maybe in the next couple of weeks).
  • I told you about a month ago that I figured out the product I was going to develop to start my micro-isv. My progress on that front has been limited. However, I am fleshing out a new idea that would make that product a subset of this new, what becomes an overarching, idea. I won't say much now other than say I am looking for a couple of partners and it includes, but goes beyond, software development into the world of internet media and other information dissemination mediums.
  • I am exploring the options for a webhost. I believe I have narrowed my choice down to 1, but I have an outstanding question to their sales department before I can say for sure. The hard part was to choose to go with a Linux based host over Windows because Windows is what I know.
  • When I choose my new webhost, I believe I am going to move this blog from its current home ( to the new webhost via The reason for this is two fold - (1) Consolidation of all blogs and websites at one place (2) A learning experience about and the migration process. I have never self-hosted a blog before.
  • I have gone totally Mac. Well, that is a little disingenuous, I suppose. I am running Mac OS X Leopard as my primarily operating system and running Windows Vista via VMWare Fusion (primarily because my current consulting gig requires it). This configuration is just awesome!! I love it!!! I am beginning to love Mac OS X as much as Windows. Also, I just bought a 20" Apple Cinema Display on Ebay that I expect to get today or tomorrow.
I will provide more detailed posts on any of these bullet items as warranted.

Is Changing the Look and Feel of a Blog a Good Idea?

If you have kept up with my blog with any regularity, you will notice as you read this post that I changed the look and feel of the blog(this assumes you are reading this at and not from an RSS Reader).

I use to host my blog. You are given the choice of 60 or so presentation options. I have been using the default presentation ever since this blog's inception.

This is Wordpress' default presentation, and the one I was using until today:


You can pay $15/year to customize the presentation, but I am not a big CSS guy and have decided to go with what is offered to me by Wordpress.

Anyway, given that I am relatively new to the blogging world, I got to wondering whether it was a good or bad idea to change the presentation (look and feel) of your blog? Will you lose readers because they don't like change? Or may you gain readers because your blog looks better? Or does it not matter a single bit?

My theory is that it doesn't matter what your blog looks like if you have interesting content that people want to read (well, I guess I can concoct some images in my head that would make people shy away -- plaid background with yellow polka dots come to mind).

Any expert bloggers out there have an opinion on this?

Feeling Small in the Blogosphere

Ok, maybe being happy with my 1000th visitor was not such a big deal after all. I was reading Robert Scoble's blog today and he, coincidentally, advertised his current statistics. When your (0,0) coordinate on your stats graph is 6000, you are probably getting a bit of readership. Can you guess which graph is mine and which graph is Robert's? Hey, I must be doing something right as he does use WordPress too :-) 



I Hit the 1000 Blog Visit Milestone!!

OK, it is not a defined milestone. I am sure that is not such a wonderful feat, and my hope is that 1/2 of those aren't my own visits ;-) , but according to my WordPress statistics, I have had 1002 visits to my blog. I am hoping the next 1000 comes much quicker. My blogging is going to change gears a bit from my previous topics about leaving my former company to now starting my own business. After a lot of thinking, and a couple of possible opportunity requests, I have made the decision to go it alone (for now) and try to become a Micro-ISV. I will continue to contract as good opportunities arise (I am currently doing one now), preferably part-time, but my main focus over the next 6 months is going to be getting my Micro-ISV started.

My next post(s), which I expect to today, will be about the methodology I am following to start the business.