Installing Movable Type 5 CMS
A CMS (content management system) keeps track of the design and all the posts in a website. |
|
This site runs on Movable Type 5
OS. The key benefit about Movable type versus all other blog platforms and CMS (content management systems) is that Movable Type creates static
HTML (hypertext markup language) pages.
What Wordpress calls a static page is not really static. Wordpress creates that page from a database
when you load the page into your browser. There is a static page plug-in to Wordpress, but plug-ins are notorious for causing problems in any
software platform.
In 2011, I installed Movable Type 5OS, the
open-source version of Movable Type. I had tried it with a different site I hosted on 1&1. As soon as I got a long post and a few
entrees, I would get "500 internal server error". Forums explained that 1&1 starves their servers for resources and that is what causes
these errors. So when it came time to move my rako.com
|
domain to a new server, I chose Dreamhost, which is supposed to be much better at
running Movable Type.
As with any software product over 35 lines,
Movable Type is complex to the point of being evil. The misery was exacerbated on the 1&1 server because the Movable Type installation
wizard does not work. On Dreamhost the wizard works fine, but it is still important to know what is going on when things inevitably break. I
should also mention that the Movable Type database you install to store all the information on the site has hard-coded path-names of your
web-server, so that makes the installation completely non-portable. You can't just copy the database to a new server and copy the install to a
new web server and expect it to work. It is easier to rebuilt the whole site from scratch if you haven't done a lot of work on it. |
|
|