rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <mpie...@cs.indiana.edu>
Subject Re: [jira] [Created] (RAVE-45) Portal host/ip configuration (Non-localhost support)
Date Wed, 01 Jun 2011 14:34:45 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't consider it to be a blocker.  I did successfully run rave and
shindig on separate tomcat servers by just changing the
portal.properties file.  It did take some manual configuration of
shindig on the second tomcat server, of course.


Marlon


On 6/1/11 10:24 AM, Franklin, Matthew B. wrote:
> Does the community feel that this is a blocker for the 0.1 release?
> 
> If not, I think we should change it to a feature and add it to 0.2.
> 
> -Matt
> 
> On 5/31/11 8:44 PM, "Zhenhua (Gerald) Guo (JIRA)" <jira@apache.org> wrote:
> 
>> Portal host/ip configuration (Non-localhost support)
>> ----------------------------------------------------
>>
>>                 Key: RAVE-45
>>                 URL: https://issues.apache.org/jira/browse/RAVE-45
>>             Project: Rave
>>          Issue Type: Bug
>>            Reporter: Zhenhua (Gerald) Guo
>>             Fix For: 0.1-INCUBATING
>>
>>
>> Currently, all configured hosts are "localhost" by default.  Non-local
>> access should be supported as well.  I can think of two places that need
>> to be changed (at least).
>> - In file portal.properties, portal.opensocial_engine.root needs to be
>> configured according to host domain/ip.
>> - When gadgets are rendered, they point to
>> "http://localhost:8080/gadgets/ifr?......". They also should be
>> configured accordingly.  (I guess this is related to Shindig config).
>>
>> Either automatic or manual configuration may work.
>> - automatic configuration: when rave portal is built, host/ip is detected
>> automatically (by some script or maven task) and filled into config files.
>> - manual configuration: the user who builds rave portal provide this
>> piece of information.
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN5k4FAAoJEOEgD2XReDo5dNkIAJxM5kwMoi40QdTASXdE+cad
jjHGVPrSXmVhz/XCI8bjVi+ejqzxPdf0Xo3CAjy8IiR5yfwH/uVtlit+AB3Rskvl
xRA60320MxAq2UhOKXOhiU5hG0teS3ZEby2h/kQL6DAimyfNZhAhNT+4bmDxQm4M
ATpDXxEKigquz5ERmsJklKzwQNUFwVCzU+uocKpzAYxus0iqDP9OO/ReYLHlspQk
sSjGe0CrfM8kUNsuhQM4uQF8CENQWJdTyZStPQvL9onWr1NMhUNVxrsIjY8VF6A3
xERmmtch38zEcszxOcDR9E/8fxvs7GPe1SEpQnFA2whKuxiHuvX2+tHPOKAgKTI=
=7Gox
-----END PGP SIGNATURE-----

Mime
View raw message