[Zope-Checkins] CVS: Zope/doc - ENVIRONMENT.txt:1.1.2.1

[Andreas Jung]

Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv21787

Added Files:
      Tag: ajung-topicindex
	ENVIRONMENT.txt 
Log Message:
added


=== Added File Zope/doc/ENVIRONMENT.txt ===
Usage of environment variables:


DISALLOW_LOCAL_PRODUCTS

    unknown


INSTANCE_HOME

    If an INSTANCE_HOME is defined and has a 'lib/python'
    subdirectory, it will be added to the front of the Python path.
    INSTANCE_HOME is usually used to seperate the Zope core installation
    from application code and third-party modules/products.

    See also SOFTWARE_HOME


SOFTWARE_HOME 
    
    The SOFTWARE_HOME usually keeps the directory name of the 
    Zope core installation.


    Order of product initialization:
        
        All Products are initialized in ascending alphabetical order by
        product name, regardless of whether an INSTANCE_HOME exists.
        If two products with the same name exist in both SOFTWARE_HOME
        and INSTANCE_HOME, the order in which they appear in
        Application.Products.__path__ determines whether they
        are loaded first or second.

    See also INSTANCE_HOME


NO_SECURITY

   Unknown. Used by TAL


PROFILE_PUBLISHER

    If set, Zope is forced profile every request of the ZPublisher.
    The profiling information is written to the value of the
    PROFILE_PUBLISHER.


CLIENT_HOME

    Used by ZEO clients to easily keep distinct pid and log files.
    

SUPPRESS_ACCESSRULE

    If set, all SiteRoots are suppressed (used by SiteAccess products).


SUPPRESS_SITEROOT

    If set, all site access rules are suppressed (used by SiteAccess products).


ZDAEMON_MANAGED

    Used for internal purposes of zdaemon


Z_DEBUG_MODE
 
    Run Zope in debug mode. Same as -D options (z2.py)


ZDIR

    Only used by Zope when running with PCGI. This variable holds the
    directory of your Zope installation.


ZEO_CLIENT
    
    Used by ZEO


Z_MAX_STACK_SIZE

    This variable allows you to customize the size of the Zope stack (default 100).
    !!!


ZOPE_READ_ONLY

    If this variable is set, then the database is opened in read only mode.  If
    this variable is set to a string parsable by DateTime.DateTime, then the
    database is opened read-only as of the time given.  Note that changes made by
    another process after the database has been opened are not visible.


ZOPE_SECURITY_POLICY

    If this variable is set to "PYTHON", Zope will use the traditional
    Python based AccessControl implementation. By default and for performance
    reasons Zope will use the cAccessControl module (Zope 2.5+)


Z_REALM

    unknown


BOBO_REALM

    unknown


STUPID_LOG_FILE="path"

    The stupid file logger writes Zope logging information to a file.
    It is not very smart about it - it just dumps it to a file and the
    format is not very configurable - hence the name.

    See also LOGGING.txt


ZSYSLOG="/dev/log"

    Setting this environment variable will cause Zope to try and write
    to the named UNIX domain socket (usually '/dev/log').  This will only 
    work on UNIX.

    See also LOGGING.txt


ZSYSLOG_FACILITY="facilityname"

    Setting this environment variable will cause Zope to use the
    syslog logger with the given facility. This environment variable
    is optional and  overrides the default facility "user". This will
    only work on UNIX.

    See also LOGGING.txt


ZSYSLOG_SERVER="machine.name:port"

    Setting this environment variable tells Zope to connect a UDP
    socket to machine.name (which can be a name or IP address) and
    'port' which must be an integer.  The default syslogd port is '514' 
    but Zope does not pick a sane default, you must specify a port.
    This may change, so check back here in future Zope releases.

    See also LOGGING.txt