System-Wide Configuration Settings

From FreeDESK
(Difference between revisions)
Jump to: navigation, search
 
(One intermediate revision by one user not shown)
Line 5: Line 5:
 
=== system.live ===
 
=== system.live ===
 
Determines if the system is live e.g. can be logged into and interacted with if set to 1
 
Determines if the system is live e.g. can be logged into and interacted with if set to 1
 +
 +
== Authentication Settings ==
 +
 +
=== auth.default ===
 +
The default authentication method for users (overriden by a user-specific setting), 'standard' means use in-built DB/password authentication.
 +
 +
== Language ==
 +
 +
=== language.default ===
 +
Default language for the system (usually English), not required as is defaulted to English in code. Warning changing this may have negative effects as English should always be the fallback language.
 +
 +
=== language ===
 +
The standard language for your installation (can be overriden with user-specific settings), set this rather than language.default to change your install language
  
 
== Logging ==
 
== Logging ==

Latest revision as of 23:27, 30 May 2012

Contents

[edit] Introduction

[edit] System Settings

[edit] system.live

Determines if the system is live e.g. can be logged into and interacted with if set to 1

[edit] Authentication Settings

[edit] auth.default

The default authentication method for users (overriden by a user-specific setting), 'standard' means use in-built DB/password authentication.

[edit] Language

[edit] language.default

Default language for the system (usually English), not required as is defaulted to English in code. Warning changing this may have negative effects as English should always be the fallback language.

[edit] language

The standard language for your installation (can be overriden with user-specific settings), set this rather than language.default to change your install language

[edit] Logging

[edit] log.level

Sets the system-wide logging level, events only of this level or below will be logged (10 means log just about everything, 1 is a critical event and 0 a fatal error), usually 5 is a good idea for running

[edit] log.purge

Days after which log entries are purged (from the standard internal database store only, does not affect external logging such as syslog). 0 means keep forever. Defaults to 30 if not set.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox