I am not too familiar about PHP version of Shindig.

I am including Bastian Hoffman who is active committer for Apache
Shindig PHP. Maybe he could help more regarding serving up features
for Shindig in PHP.

- Henry

On Thu, Jan 27, 2011 at 1:09 AM, Wouter Charle <[email protected]> wrote:
> Hi Henry
>
> I'm not sure about what you mean by root application, but here is how I've
> setup Shindig and Partuza:
> I've set up 2 virtual hosts: http://shindig/ and http://partuza/
> I added a local.php file in <shindig>/config/
> Content of local.php:
> <code>
> <?php
> $shindigConfig = array(
>    'person_service' => 'PartuzaService',
>    'activity_service' => 'PartuzaService',
>    'app_data_service' => 'PartuzaService',
>    'messages_service' => 'PartuzaService',
>    'oauth_lookup_service' => ''PartuzaOAuthLookupService',
>    'extension_class_paths' => '../../partuza/Shindig'
> );
> </code>
> And I'm sure the extension_class_paths setting is correct.
> I hope this answers your question?
> Apparently Partuza knows about Shindig being on http://shindig/ since the
> request url for osapi.js is http://shindig/gadgets/files/container/osapi.js
> Is there some test I could do to check if Shindig is set up correctly?
>
> Many thanks!!
>
> On Wed, Jan 26, 2011 at 9:29 PM, Henry Saputra <[email protected]>wrote:
>
>> Did you install Shindig as root application?
>>
>> - Henry
>>
>> On Wed, Jan 26, 2011 at 5:32 AM, Wouter Charle
>> <[email protected]> wrote:
>> > Hi, I'm trying out Shindig using Partuza and although everything seems
>> fully
>> > functional (did not see broken functionallity), I see the following error
>> in
>> > Chrome's console:
>> > Failed to load resource: the server responded with a status of 404 (Not
>> > Found)
>> >
>> > Header:
>> >
>> >   1. *
>> >      1. Request URL:
>> >      http://shindig/gadgets/files/container/osapi.js
>> >      2. Request Method:
>> >      GET
>> >      3. Status Code:
>> >      404 Not Found
>> >      4. Request Headers
>> >         1. Accept:
>> >         */*
>> >         2. Accept-Charset:
>> >         ISO-8859-1,utf-8;q=0.7,*;q=0.3
>> >         3. Accept-Encoding:
>> >         gzip,deflate,sdch
>> >         4. Accept-Language:
>> >         en-US,en;q=0.8
>> >         5. Connection:
>> >         keep-alive
>> >         6. Host:
>> >         shindig
>> >         7. Referer:
>> >         http://partuza/home
>> >         8. User-Agent:
>> >         Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.10
>> >         (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
>> >         5. Response Headers
>> >         1. Connection:
>> >         close
>> >         2. Content-Encoding:
>> >         gzip
>> >         3. Content-Length:
>> >         59
>> >         4. Content-Type:
>> >         text/html
>> >         5. Date:
>> >         Wed, 26 Jan 2011 13:29:52 GMT
>> >         6. Server:
>> >         Apache/2.2.16 (Ubuntu)
>> >         7. Vary:
>> >         Accept-Encoding
>> >         8. X-Powered-By:
>> >         PHP/5.3.3-1ubuntu9.3
>> >         *
>> >      1.
>> >
>> > Content: only an empty line, that's it
>> >
>> > Is this something to bo worried about, or just normal? What implications
>> > does it have?
>> > Many thanks!!
>> >
>>
>>
>>
>> --
>> Thanks,
>> Henry
>>
>



-- 
Thanks,
Henry

Reply via email to