[
https://issues.apache.org/jira/browse/JAMES-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199773#comment-15199773
]
Ioan Eugen Stan edited comment on JAMES-1709 at 3/17/16 4:01 PM:
-----------------------------------------------------------------
Hello Matthieu,
Doesn't this make more sense to be handled via configuration file? The
configuration should be external to any Jar file.
Environment variable makes sense for stuff like ports that can be changed
easily.
The domain that a mail server handles can be changed via a configuration
management tool like the CLI or a web configuration tool and should be
persisted across restarts.
That is my understanding and the way I see it. Does it make sense to you? If
right now it's not easy to supply domains via configuration maybe it makes sens
to re-factor that area.
was (Author: ieugen):
Hello Matthieu,
Doesn't this make more sense to be handled via configuration file? The
configuration should be external to any Jar file.
Environment variable makes sense for stuff like ports that can be changed
easily.
The domain that a mail server handles can be changed via a configuration
management tool like the CLI or a web configuration tool and should be
persisted across restarts.
That is my understanding and the way I see it. Does it make sense to you?
> Domain initialization on start
> ------------------------------
>
> Key: JAMES-1709
> URL: https://issues.apache.org/jira/browse/JAMES-1709
> Project: James Server
> Issue Type: Improvement
> Components: James Core
> Reporter: Matthieu Baechler
>
> When somebody launch James for the first time, he often wants to have a
> domain configured automatically (without using the cli).
> James should be able to handle a environment variable DOMAIN. Once started,
> the domain should be present into James.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
