Project

General

Profile

Revision b2346a00

IDb2346a0041bd0a172e522daa9f54be96dd8642f2
Parent 24d74687
Child 72ec8dbf

Added by Francois POIROTTE about 14 years ago

Mise à jour des settings de VigiBoard pour permettre le changement de l'ordre de tri
entre l'horodatage et l'état Nagios facilement.

git-svn-id: https://vigilo-dev.si.c-s.fr/svn@2617 b22e2e97-25c9-44ff-b637-2e5ceca36478

View differences:

development.ini
22 22 
[app:main]
23 23 
use = egg:vigiboard
24 24 

  		




  25
  
  
    
db_basename=


  		




  26
  
  
    
;password_hashing_function=md5


  		




  
  25
  
    
db_basename=vigilo_


  		




  
  26
  
    
password_hashing_function=md5


  		




  27
  27
  
    
lang=fr


  		




  28
  28
  
    
use_kerberos=False


  		




  29
  29
  
    

  		




  ......




  45
  45
  
    
; See http://www.w3.org/TR/CSS21/fonts.html#font-size-props


  		




  46
  46
  
    
vigiboard_font.size = 10px


  		




  47
  47
  
    

  		




  
  48
  
    
; Indique si le tri des événements se fait d'abord sur l'état Nagios


  		




  
  49
  
    
; puis l'horodatage de l'événement, ou bien l'inverse.


  		




  
  50
  
    
; Dans tous les cas, d'autres critères de tri interviennent avant


  		




  
  51
  
    
; (état d'acquittement et priorité ITIL).


  		




  
  52
  
    
state_first = True


  		




  48
  53
  
    

  		




  49
  54
  
    
full_stack = true


  		




  50
  55
  
    
cache_dir = %(here)s/data


  		




  ......




  60
  65
  
    

  		




  61
  66
  
    
# DB - sqlite fails, not postgresql ready, use mysql for now


  		




  62
  67
  
    
sqlalchemy.url=postgres://vigilo:vigilo@localhost/vigilo


  		




  63
  
  
    
#echo shouldn't be used together with the logging module.


  		




  64
  68
  
    
sqlalchemy.echo = false


  		




  65
  69
  
    
sqlalchemy.echo_pool = false


  		




  66
  70
  
    
sqlalchemy.pool_recycle = 3600


  		




  67
  71
  
    

  		




  68
  
  
    
# if you are using Mako and want to be able to reload


  		




  69
  
  
    
# the mako template from disk during the development phase


  		




  70
  
  
    
# you should say 'true' here


  		




  71
  
  
    
# This option is only used for mako templating engine


  		




  72
  
  
    
# WARNING: if you want to deploy your application using a zipped egg


  		




  73
  
  
    
# (ie: if your application's setup.py defines zip-safe=True, then you


  		




  74
  
  
    
# MUST put "false" for the production environment because there will


  		




  75
  
  
    
# be no disk and real files to compare time with.


  		




  76
  
  
    
# On the contrary if your application defines zip-safe=False and is


  		




  77
  
  
    
# deployed in an unzipped manner, then you can leave this option to true


  		




  78
  
  
    
templating.mako.reloadfromdisk = true


  		




  79
  
  
    

  		




  80
  
  
    
# the compiled template dir is a directory that must be readable by your


  		




  81
  
  
    
# webserver. It will be used to store the resulting templates once compiled


  		




  82
  
  
    
# by the TemplateLookup system.


  		




  83
  
  
    
# During development you generally don't need this option since paste's HTTP


  		




  84
  
  
    
# server will have access to you development directories, but in production


  		




  85
  
  
    
# you'll most certainly want to have apache or nginx to write in a directory


  		




  86
  
  
    
# that does not contain any source code in any form for obvious security reasons.


  		




  87
  
  
    
#


  		




  88
  
  
    
#templating.mako.compiled_templates_dir = /some/dir/where/webserver/has/access


  		




  89
  
  
    

  		




  90
  72
  
    
# WARNING: *THE LINE BELOW MUST BE UNCOMMENTED ON A PRODUCTION ENVIRONMENT*


  		




  91
  73
  
    
# Debug mode will enable the interactive debugging tool, allowing ANYONE to


  		




  92
  74
  
    
# execute malicious code after an exception is raised.


  		




  ......




  117
  99
  
    
qualname = vigiboard


  		




  118
  100
  
    

  		




  119
  101
  
    
[logger_sqlalchemy]


  		




  120
  
  
    
level = DEBUG


  		




  
  102
  
    
level = INFO


  		




  121
  103
  
    
handlers = console


  		




  122
  104
  
    
#sql_log


  		




  123
  105
  
    
qualname = sqlalchemy.engine


  		












Also available in:  Unified diff