[Sommaire] [Imprimer]

   1  <?php
   2  ##########################################################
   3  # WebCalendar Site Settings
   4  #
   5  # You can edit this file by hand.  Start by copying settings.php.orig
   6  # to be settings.php
   7  #
   8  # This is not really a php file, but we use the .php file extension to
   9  # prevent malicious users from downloading this file to obtain our
  10  # database login.
  11  #
  12  # When you're done here, try accessing WebCalendar as an admin
  13  # user and go to the System Settings page (admin.php) to change system
  14  # settings.
  15  #
  16  # For ODBC use, ignore the db_host value and set 
  17  # db_database to your full DSN
  18  ##########################################################
  19  
  20  # database settings see notes above
  21  db_type: mysql
  22  db_host: localhost
  23  db_login: webcalendar
  24  db_password: webcal01
  25  db_database: intranet
  26  db_persistent: true
  27  
  28  # Read-only mode: You can set this to true to create a read-only calendar.
  29  # If you enable $single_user_login (below), no login will be required,
  30  # making this a publicly viewable calendar.  In order to add events to
  31  # a setup like this, you will need to setup another installation of this
  32  # application that is not read-only.
  33  # If $readonly is enabled in multi-user mode, only admin users will able
  34  # to add/edit/delete events.
  35  # NOTE: Approvals are not disabled in read-only.  You must also disable
  36  # approvals if you don't want to use them.
  37  # NOTE #2: Using $readonly has mostly been superceded by the new public
  38  # access calendar (added in version 0.9.35) which allows
  39  # a public access calendar with no login or a regular calendar user with
  40  # a valid login.  This is configured in the admin web interface.
  41  # If you want to use the new system (recommended), leave this $readonly
  42  # setting set to "false".
  43  readonly: false
  44  
  45  # Are you setting this up as a multi-user system?
  46  # You can always start as a single-user system and change to multi-user
  47  # later.  To enable single-user mode, uncomment out the following line
  48  # and set it to a login name (that you would use if you ever switched to
  49  # multi-user).  In single-user mode, you will not be prompted for a login,
  50  # nor will you be asked to select participants for events.
  51  # NOTE: If you select single-user and then upgrade to multi-user later,
  52  # you'll have to add in the login name you've set below to the cal_user
  53  # table.  You will be able to do this from the web admin interface.
  54  # Set $single_user to either true or false.  If true, make sure
  55  # $single_user_login is defined.
  56  single_user: false
  57  #single_user_login: cknudsen
  58  
  59  # Do you want to use web-based login or use HTTP authorization?
  60  # NOTE: You can only use HTTP authorization if PHP is built as
  61  # an Apache module.
  62  # NOTE #2: There's no need to use this if you're running single
  63  # user mode.
  64  # Set the following to true to use http-based authorization.
  65  # If you want to setup a public calendar with HTTP-based authentication,
  66  # see FAQ in WebCalendar-SysAdmin.html for instructions.
  67  use_http_auth: false
  68  
  69  # user authentication module (user.php, user-ldap.php, user-nis.php)
  70  # Note: if you enable LDAP support (with user-ladp.php), you will also
  71  # need to modify user-ldap.php to configure some settings.
  72  user_inc: user.php
  73  
  74  # end
  75  ?>