This is documentation about a configuration directive, which can be placed within Movable Type’s core configuration file,
mt-config.cgi, to customize the behavior of the system.
The absolute file system path to the
This value corresponds to the absolute URL path or fully-qualified domain name URL specified in StaticWebPath.
Tip: If not configured, it is assumed that the
mt-staticdirectory is located in the application directory. Thus the
StaticFilePathdirective is only required if the
mt-staticdirectory has been moved out of the Movable Type application directory.
Note that the StaticFilePath should not point to your blog, and Movable Type should not be installed in the same location you want your blog to appear. For organization and clean functionality, Movable Type should be installed in its own folder; your blog can be set up anywhere outside of this folder.
Filesystem path. Default is to assume that filepath is the value of
CGIPath + “mt-static/”
If the application directory is located at:
URL: http://example.com/cgi-bin/mt/ Filepath: /var/www/cgi-bin/mt/
…and static files cannot be served from the
cgi-bin directory, then you have two choices:
/var/www/cgi-bin/mt/mt-static/via symlink, Apache alias, etc.
mt-staticdirectory is still in the application directory there is no need to use the
StaticFilePathconfig directive. The
mt-config.cgifile would look like this:
CGIPath http://example.com/cgi-bin/mt/ StaticWebPath http://example.com/mt-static/
mt-staticdirectory to the web root directory:
and then set the
StaticFilePathconfig directive to this location:
The following three path settings would then be in the
CGIPath http://example.com/cgi-bin/mt/ StaticWebPath http://example.com/mt-static/ StaticFilePath /var/www/html/mt-static/