Next Previous Contents

3. Configuration

3.1 masser.conf

max_cycles

number of requests; after processing them masser will be restarted (exits and fast-cgi will start it again), recommended value is between 100 - 2000

path

list of directories, where masser will find application configurations and files (semicolon separated)

img

image directory (URL, can be relative to masser.fcgi)

log_file

full path and name of main masser log

log_error

where to write errors:

log_warn

where to write warnings

log_info

where to write information messages

log_debug

where to write debug messages

debug

if set, masser is running in debug mode

content-type

Content-Type setting for generated pages (used in page_header function)

app_path

URL to masser itself, without protocol specification (http or https is added automatically), for example ip_or_name_of_server/path/masser.fcgi

access_log

full path with filename, where information about accesses to masser will be written. If not set, no log will be created.

access_log_format

access_log format, you can use following variables:

performance_log

full path with filename, where information about masser performance will be written. If not set, no log will be created.

performance_log_format

performance_log format, you can use following variables:

max_memory_size

maximal memory size allocated by masser; if masser is bigger than this value, it will exit to release memory. Checkout is performed after processing each request.

at this time works only on Linux

pending_transaction_rollback

masser checks if there are no started transactions after processing all actions and pages in request (in active database connections). If there are any, it writes error to log and - if this parameter is set - performs rollback.

3.2 <app>.conf

Application configuration files.

path

this value will be added to path from masser.conf only for this application, other applications will not be influenced

languages

list of languages in which application texts exist (comma separated), uppercase is recommended

log_file

full path and filename of log file of application

log_error

where to write errors:

log_warn

where to write warnings

log_info

where to write information messages

log_debug

where to write debug messages

dbX_*

db connection settings, X is number from 1 to 5:

write_code_dir

if set, masser will write to given directory every (compiled) source code (both action and page) before it tries to run it; name is composed like this: <app>_<type>_<name>.code, where <app> is name of application, <type> is type (pg - page, ac - action) and <name> is object name

db_trace

database trace level for DeltaX::Database, this is used if no dbX_trace is set

db_stat

statistics level for DeltaX::Database, this is used if no dbX_stat is set; syntax is: db_stat = type[,max_high[,max_all]], where:

db_statfile

where to write statistics (full path with filename), this is used if no dbX_statfile is set

Application configuration file can have any other parameters, masser ignores them and they are for application use.


Next Previous Contents