[
https://issues.apache.org/jira/browse/JAMES-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008842#comment-17008842
]
Matthieu Baechler commented on JAMES-3019:
------------------------------------------
Hi [~sergey-b] and thank you for opening this issue.
I worked on this very topic recently and came to the following conclusions:
* we should behave like any system daemon, that is : read configuration from
/etc, write data to /var, and so on, by default
* we should allow to override each directory from the command line
* we should provide a real command line "launcher" to implement these options
WDYT about this?
> Clear and flexible handling of base directory
> ---------------------------------------------
>
> Key: JAMES-3019
> URL: https://issues.apache.org/jira/browse/JAMES-3019
> Project: James Server
> Issue Type: Improvement
> Affects Versions: 3.3.0, 3.4.0
> Reporter: Sergey B.
> Priority: Major
>
> We need to have a single value from which all relative urls are evaluated.
> Now some urls pointing to the same places are specified by different values.
> For example var directory for database storage is presented by the value
> '../var/' in database.url property, while the same directory for
> MailRepository is designated by 'file://var/.
> It's confusing. I suggest we make an improvement.
> # There must be a single value of basedir, from which all relative urls are
> evaluated.
> # Algorithm of evaluation of default basedir value must be documented.
> # Default basedir must be at top level of all resources. I. e. there must be
> no paths like ../.
> # Effective basedir must be logged.
> # There must be an opportunity for users to specify their own basedir on
> server startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
