You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2014/02/02 22:26:10 UTC

[jira] [Updated] (WOOKIE-361) Allow configuration of virtual host using environment variables as well as properties configuration

     [ https://issues.apache.org/jira/browse/WOOKIE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wilson updated WOOKIE-361:
--------------------------------

    Fix Version/s:     (was: 1.0.0)
                   2.0.0

> 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
>             Fix For: 2.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)