1 # Example configuration file for htsn-import. For this to take effect, you
2 # would need to place it in either the user or global configuration
5 # For a user, that's either $HOME/.htsn-importrc on Unix or
6 # %APPDATA%\.htsn-importrc (e.g. C:\Users\<username>\Application
7 # Data\.htsn-importrc) on Windows.
9 # The global configuration directory is determined by Cabal. The
10 # "sysconfdir" parameter during the "configure" step will be used. On
11 # Unix, it's probably /etc, and this file will need to go in
15 # The RDBMS backend to use. Valid choices are "Sqlite" and
16 # "Postgres". Capitalization is important, sorry.
20 # backend = "Postgres"
23 # The connection string used for connecting to the database backend
24 # given by the "backend" option. The default is appropriate for
25 # the "Sqlite" backend.
29 # connection_string = "dbname=htsn user=postgres"
32 # If you specify a file path here, logs will be written to it
33 # (possibly in addition to syslog). Can be either a relative or
34 # absolute path. It will not be auto-rotated; use something like
39 # log_file = "/var/log/htsn/htsn.log"
42 # How verbose should the logs be? Valid levels are,
44 # "INFO", "WARNING", "ERROR"
46 # (there are others, but we don't emit them.)
50 # log_level = "WARNING"
53 # Remove successfully processed files. If you enable this, you can see
54 # at a glance which XML files are not being processed, because they're
55 # all that should be left.
62 # Do you want to log to syslog? On Windows this will attempt to
63 # communicate (over UDP) with a syslog daemon on localhost, which will
64 # most likely not work.