[
https://issues.apache.org/jira/browse/WOOKIE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419868#comment-13419868
]
Scott Wilson commented on WOOKIE-361:
-------------------------------------
I guess what I mean is, use Wookie's own settings where they are present, but
if not, and if Shindig properties are set, use those.
Alternatively, we could get the Rave deployment to sort this all out in one
place.
> Allow configuration of virtual host using environment variables as well as
> properties configuration
> ---------------------------------------------------------------------------------------------------
>
> Key: WOOKIE-361
> URL: https://issues.apache.org/jira/browse/WOOKIE-361
> Project: Wookie
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.11.0
> Reporter: Scott Wilson
>
> Currently, when you deploy Wookie using a proxy/vhost you edit
> widgetserver.properties with the scheme/host/port info to use.
> However, when Wookie is deployed using Rave, you may use environment
> variables to configure Shindig:
> shindig.host=dev.ict-omelette.eu
> shindig.port=80
> shindig.contextroot=
> However you still have to configure Wookie separately.
> However we could do the config check in the following order:
> 3. Check for shindig environment variables
> 2. Check for environment variables (widget.server.hostname etc)
> 1. Check widgetserver.properties as usual
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
