Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0005567Openbravo ERPZ. Otherspublic2008-10-17 15:472013-06-18 13:03
plujan 
jpabloae 
normalminorhave not tried
closedfixed 
5
pi 
2.50pi 
Core
No
0005567: Add self-documentation to configuration files options
Openbravo ERP is turning more and more complex on each new version. And configuration files, like Openbravo.properties can be modified on several ways.
Although config is usually written on installations, sometimes in necessary to hack some parameters.

As an example, look at Apache Tomcat configuration file, server.xml. Or PostgreSQL's pg.conf file. Every parameter is explained, some examples are shown and the most common options are described. A complete how-to about hacking the configuration is on the file itself. This do not avoid config issues, of course, but the most basic questions about what would happen when modifying a value are answered there.
ReleaseCandidate
Issue History
2008-10-17 15:47plujanNew Issue
2008-10-17 15:47plujanAssigned To => pjuvara
2008-10-17 15:47plujansf_bug_id0 => 2174817
2008-10-17 15:47plujanRegression testing => No
2008-10-17 17:43pjuvaraAssigned Topjuvara => jpabloae
2008-10-17 17:43pjuvaraStatusnew => acknowledged
2008-10-17 17:43pjuvaraTarget Version => 2.60
2008-10-17 17:43pjuvaraSummaryConfiguration files options are not self-documented => Add self-documentation to configuration files options
2008-10-17 17:44pjuvaraStatusacknowledged => scheduled
2008-10-17 17:44pjuvarafix_in_branch => trunk
2008-10-17 17:44pjuvaraTag Attached: ReleaseCandidate
2008-11-03 15:37svnbotCheckin
2008-11-03 15:37svnbotNote Added: 0009942
2008-11-03 15:37svnbotsvn_revision => 9577
2008-11-17 07:36pjuvaraTarget Version2.60 => 2.50
2008-11-17 07:36pjuvarafix_in_branchtrunk =>
2008-11-17 07:37pjuvaraStatusscheduled => resolved
2008-11-17 07:37pjuvaraFixed in Version => 2.50
2008-11-17 07:37pjuvaraResolutionopen => fixed
2008-11-26 20:20pjuvaraStatusresolved => closed
2008-12-06 17:20plujanStatusclosed => new
2008-12-06 17:20plujanResolutionfixed => open
2008-12-06 17:20plujanNote Added: 0011017
2008-12-06 17:20plujanFixed in Version2.50 =>
2008-12-13 16:23jpabloaeNote Added: 0011292
2009-01-26 17:19svnbotCheckin
2009-01-26 17:19svnbotNote Added: 0012639
2009-01-26 17:19svnbotsvn_revision9577 => 12270
2009-01-26 17:23jpabloaeStatusnew => scheduled
2009-01-26 17:23jpabloaefix_in_branch => trunk
2009-01-26 17:23jpabloaeNote Added: 0012640
2009-01-26 17:28jpabloaeStatusscheduled => resolved
2009-01-26 17:28jpabloaeFixed in Version => trunk
2009-01-26 17:28jpabloaeResolutionopen => fixed
2009-05-26 18:02pjuvaraStatusresolved => closed
2009-11-09 15:01jpabloaeProjectOpenbravo ERP => Documentation
2009-11-10 12:57jpabloaeCategoryD. Documentation => Z Other
2013-06-18 13:00psanjuanProjectDocumentation => Openbravo ERP
2013-06-18 13:03psanjuanCategoryZ Other => Z. Others

Notes
(0009942)
svnbot   
2008-11-03 15:37   
Repository: openbravo
Revision: 9577
Author: jpabloae
Date: 2008-11-03 15:37:50 +0100 (Mon, 03 Nov 2008)

Related to issue 5567: Reorganize main properties file

---
U trunk/config/Openbravo.properties.template
---

https://dev.openbravo.com/websvn/openbravo/?rev=9577&sc=1 [^]
(0011017)
plujan   
2008-12-06 17:20   
I do not agree about closing this feature request. Please note that the request is about a self-documented properties file. Since 2.50 alpha that file has titles, but is far from self-documented. I added some examples (Tomcat's configuration file and Postgres' one).
Apart from the title, a brief description of the parameter and a detail of the available options is part of a good self-documented file.

Note for QA deparment: please review feature request closing policies to avoid closing incomplete requests.
(0011292)
jpabloae   
2008-12-13 16:23   
I'm not very friend of long self-documented configuration files. It means maintaining the documentation in 2 places, and most of the times the amoutn of documentation you can include in the file is so amll that you always end up reading the complete one.

You put Tomcat as an example, but if you take that file (conf/server.xml), you'll see that they only refer to external documentation:

  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />

If you go to http://tomcat.apache.org/tomcat-6.0-doc/apr.html [^] , you'll see that it's not worth it to include all that information in the server.xml file.
(0012639)
svnbot   
2009-01-26 17:19   
Repository: openbravo
Revision: 12270
Author: jpabloae
Date: 2009-01-26 17:19:56 +0100 (Mon, 26 Jan 2009)

Related to issue 5567: Document Openbravo.properties file in wiki, reorder elements. Link wiki.

---
U trunk/config/Openbravo.properties.template
---

https://dev.openbravo.com/websvn/openbravo/?rev=12270&sc=1 [^]
(0012640)
jpabloae   
2009-01-26 17:23   
Openbravo.properties documented and liked to http://wiki.openbravo.com/wiki/Openbravo.properties [^]