|Local Development Configuration|
Per directory you need to specify
There are various options which have slightly different meanings based on which database system you are using. Please go to the Supported Platforms page to read about the details for your system.
In general set the option
access to T to allow access to the Web
server running heitml and
write to T to allow writes to the
database. NOTE however that some databases do not support read-only operation
or contain loopholes that permit changes even in read-only mode. You should
therefore never rely on this parameter securely blocking all database updates.
In the simplest case for ODBC on a Windows system you need to specify
datasource, which must be the name of the ODBC system data source.
See ODBC-32 for more information how to set up an
ODBC system data source.
Additionally you need to set
password if the
database system supports user authentication (like the MS SQL Server).
If the database system supports several databases per data source,
specify the database name in the ODBC System Data Source Setup.
On UNIX, there is no
datasource parameter but a
dbhost parameter. If
dbhost given, it must be
the name of the host where the database server is running, otherwise it defaults to
the local host.
A non-default port on the host where the database server is running can be configured using the
If the database system supports several databases,
dbname to specify the database. Parameters
work as on Windows.
The include path is a list of directories. When heitml looks for an include file then heitml works through all of the directories in the path. The first directory that contains the desired include file is taken.
include parameter takes a list of directory names separated by semicolons.
Directory names can be relative to the directory where the configuration file
is stored in. Take care when copying configuration files in conjunction with
You can set the option
secure to off to enable the < shell > tag and
other heitml functions to access the file system. It is however
useful to do that only if really needed.
UNIX File Permissions for RADpage
When using RADpage on UNIX, file permissions must be configured
correctly. Otherwise, RADpage can not modify your files. Easiest (and
default) way is that all files and directories are owned by the Web server
user. For Apache, the Web server user is given by the
user configuration directive in httpd.conf.
If the value is set to nobody,
it is a good idea to change this in the context of RADpage and
create an own user id for Apache.
Alternatively, all directories containing .hei files
must belong to the Web server group (the
group configuration directive for Apache given in httpd.conf),
and the directories must be group writeable. All users using RADpage must
be members of this group and
compeditperm must be set
to g+w. Note that this setup allows anybody in the Web server group
to change everything on the Web server. For finer grain access control
see Service Providers.