1. 15 Sep, 2014 2 commits
  2. 11 Jul, 2014 2 commits
  3. 10 Jul, 2014 1 commit
  4. 01 Jul, 2014 1 commit
  5. 23 Jun, 2014 5 commits
  6. 12 Jun, 2014 1 commit
    • thorsten.vitt's avatar
      Allow overriding confserv values via config file. · 701a0e2a
      thorsten.vitt authored
      Specify a confserv property with the key prefixed with 'aggregator.rep.'
      in one of the usual configuration files or as a system property and its
      value will be used instead of the one from the confserv. Currently this
      would by only interesting for `tgcrud`, `tgsearch` and
      `tgsearch-public`.
      701a0e2a
  7. 10 Jun, 2014 3 commits
  8. 02 Jun, 2014 3 commits
  9. 26 May, 2014 1 commit
  10. 24 May, 2014 2 commits
  11. 23 May, 2014 1 commit
  12. 22 May, 2014 1 commit
  13. 17 Mar, 2014 2 commits
  14. 14 Mar, 2014 3 commits
  15. 19 Feb, 2014 3 commits
  16. 18 Feb, 2014 5 commits
  17. 17 Feb, 2014 1 commit
  18. 12 Feb, 2014 1 commit
    • thorsten.vitt's avatar
      Optionally use an external configuration file. · 0ae7a435
      thorsten.vitt authored
      When the service is set up, it will try to load configuration files:
      
      1. internal file
      2. /etc/textgrid/aggregator/aggregator.properties
      3. ~/.aggregator.properties
      
      The last one wins. The internal file will be filled with default values
      according to the profiles selected at build time. A copy of the default
      config will be generated at target/aggregator.properties; you can
      generate it manually using the resources goal, e.g.:
      mvn -Pesx1 resources:resources
      0ae7a435
  19. 11 Feb, 2014 2 commits