|
I would like to know why such app server specific configuration are stored in the database and not in configuration files. Having it the way it is now, even in 3.7.1, is really annoying – is there some benefit or reason for having it this way that I am not seeing?
Gum,
Can you let me know what you consider 'app server specific configuration' ? It's best to keep anything that can be configured through JIRA in the database. Configuring paths (index, backup, attachments) within JIRA is a lot easier than doing it in the app server, and doesn't require a reboot. However, it should be possible to set such paths in the app server (via JNDI or system properties), where it would take precedence over the database value.
See if the schema page
 helps I've added a page describing how the configuration data is stored:
http://confluence.atlassian.com/display/JIRA/Configuration+properties Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Create home directory instead of index & attachment directory
${jira.logs} = ${jira.home}/logs
Eg. people may want logs to go to /var/log/jira.log, indexes to /var/run/jira_indexes, backups to go to a partition with lots of space, etc.