These are the notes I've gathered regarding the maintenance of my (dv) base system, which was configured out-of-the-box rather inefficiently. Media Temple has since adopted some of my suggestions, so this tuning may no longer be necessary.

These are older notes and don't necessarily cover the newest versions of Wordpress and Media Temple's (dv) offerings.

I'm no longer running WordPress on my (dv), but here are the notes I wrote when I was moving my old wordpress blog. The optimization notes are probably still useful. I'm currently running Expression Engine, if anyone is curious.

Moving to Media Temple

• Wordpress and Shared Hosting - the move from smaller to larger servers, explained.
• Moving Wordpress Databases - to get around the export limitations for large blogs.
• Moving Wordpress to Media Temple - the steps taken to move my wordpress blog

General Optimization

• Configuring a Media Temple (dv) Base for Wordpress
• Other Optimizations for Media Temple (dv) Base

Troubleshooting

• Monitoring Media Temple (dv) Memory Usage
• Separate PHP Error Logs with Plesk on the Media Temple (dv)

Working Notes

Internal Dummy Connections?

I was doing some internal server optimization, and noticed a lot of error messages in /etc/httpd/logs/error_log coming from localhost (127.0.0.1) trying to hit the root directory of httpdocs. That's totally weird, so I Googled it and came up with this explanatory post. The solution to avoid errors was to create a dummy index file in the DocumentRoot. Apache still logs the access, though.