UHTML can be installed in two ways, system-wide or website local. System-wide installation is preferred, it makes UHTML available for all websites hosted on the system, but needs root privileges. Website local installation is possible without root privileges. It provides UHTML just for the particular site.
To install UHTML system-wide, the
uHMTL.pm file need to be copied into
any global perl library directory and a subdirectory
uHTML need to be
created in the same library directory. The subdirectory
uHTML will be used
for global UHTML modules.
To install UHTML locally for one website, the
uHMTL.pm file need to
be copied into the
cgi directory of the website and a subdirectory
uHTML need to be created in that directory.
Tags provided by modules copied into the
uHTML subdirectory are
immediately available. In this way complex functionalities as
catalogues or whole content management systems can
be used in a website without any additional programmer's action needed.
Not needed modules should be deleted from the
to decrease unnecessary system load.
Some tags are so specific to a particular website, that it makes no sense
to make libraries with them an keep them to be used in other websites.
Such tags get coded into modules with a name fitting the schema
*-uHTML.pm located in the
independent of the way how UHTML got installed. Tags from those modules are
bound automatically into the site.