Site Directory

Although sites can be located anywhere the web server has access, as suggested in Installation a concealed logical name for locating VWcms sites is the recommended approach.

$ DEFINE /SYSTEM /TRANSLATION=CONCEALED VWCMS_ROOT DKA0:[VWCMS.]

Create an appropriately named site directory

$ CREATE /DIRECTORY VWCMS_ROOT:[THE_EXAMPLE]

ensuring required directory protections are set.

Site Content

There are many sites providing free and commercial packages containing the essentials of a Web site.  These relatively easily can be adapted for VWcms usage.  Following the general directions provided in Website Packages.

The alternative is to construct the site essentially from scratch.  Into the site directory the required seed files need to be copied.  Seed files contain the essential elements of a VWcms site infrastructure and although all can be created manually from scratch this is a quicker route to a basic site.

$ COPY [.STARTER]*.* VWCMS_ROOT:[THE_EXAMPLE]

Mapping Rules 1

The site's URL must be mapped into server space.

<Location /the_example/>
RewriteEngine  on
RewriteRule  /the_example/(.*)  /cgi-bin/vwcms/the_example/$1
</Location>

The script rule for OSU and WASD is only required the once per VWcms.

Mapping Rules 2

VWcms only provides content from the _INDEX.HTML primary content file.  For efficiency all other site resources (CSS, images, graphics, etc.) are provided directly by the Web server.  This requires it to be configured for where to obtain these files.  VWcms uses the site name prefixed by an underscore as the root of the resource path.  Using the above "The Example" site, a graphic resource would be requested using

/_the_example/an_image.png

Therefore for each site a rule must be present that maps this to the file-system location.

Of course this is in addition to other required mapping rules.

Configuration Directives

At this point the germinal site may be accessed using a path

/the_example/

Each site can have its own confguration file _VWCMS.CONF located with the other site files and uses specific site directives.

Site configuration can use the same conditional directives described for Global Configuration (but as mentioned, not the same configuration directives).

Site directives are described in Site Directives.