(dv) 4.0 - Making It Better

  • This page was last modified on December 14, 2011, at 14:07.
The (mt) Community Wiki is a collaborative project. Any (mt) Media Temple customer or employee may contribute. Not all articles and/or content have been tested for accuracy by (mt) Media Temple.

For officially moderated and tested articles, be sure to visit our KnowledgeBase.

From (mt) Community Wiki

Under Contruction! The articles below are good to go, but more are coming!

Long story short: This is going to be a series of articles on suggestions and possible upgrades for a (dv) 4.0 to get more out of it. There will be a script made available shortly that let's you pick and choose which changes you would like to automate with just a few yes/no questions.

Currently available guides

(dv) 4.0 - Making It Better :: Upgrade to Plesk 10.3.1

(dv) 4.0 - Making It Better :: General MySQL Tuning

(dv) 4.0 - Making It Better :: General Apache Tuning

(dv) 4.0 - Making It Better :: Installing Monit

(dv) 4.0 - Making It Better :: Installing Munin

(dv) 4.0 - Making It Better :: Installing Plesk Health Monitor

(dv) 4.0 - Making It Better :: Web Accessible phpMyAdmin

(dv) 4.0 - Making It Better :: Using mod suphp with Plesk

FAQ

Does (mt) Media Temple directly support these articles? Should I submit a support request if something goes wrong?

  • No. These articles are written with the (dv) 4.0 server in mind, but there's no official ties to anything here as far as (mt) Media Temple support goes. All the standard "at your own risk" caution applies as normal for a self-managed server.

What's the idea behind this series?

  • Given the title of this wiki article, this is probably seems like a silly question. But really, the (dv) Dedicated-Virtual server presents a tricky situation for many users. Shared hosting, such as the (gs) Grid-Service isn't for everyone. Some users need configurations that shared hosting simply can't provide, and some users simply outgrow shared hosting. However, in many of these cases, it can be a monumental jump to move into a self-managed, dedicated system. The goal of these articles is to provide easily digestible help for those that want to try and bring their server to the point where it "just works" with solid levels of performance, while a few helpful tools are added along the way.

What would be considered a prerequisite to these guides?

  • You only need two things for any guide in this series. First, you need to be able to connect to your server via SSH as root. From there, if you can copy and paste, you're good to go. Every single text box that appears like the example below is intended to be copied in it's entirety and then pasted as a single command. Some are very (very) long. And there are some that more advanced users may want to edit. But no command requires anything beyond being literally copy and pasted for built-in functionality.
echo "I'm an example command (that is safe to practice with). Copy all
of me that is inside this box and then press
enter once you've pasted me into your SSH program!"

I'd like to do all of these! What order should I do them in?

  • As the list is updated, they should be kept so that the recommended path is going top to bottom.

Well I want to pick and choose! Can I?

  • Sure. Each article/guide is an independent resource. There are a few cross-references you may find, but they are always optional things you can go back and do later or just skip-over.

Where's the script that does all of this for me?!

  • It's coming as soon as possible; promise!

...still under construction...