You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Erel Segal <er...@gmail.com> on 2008/08/14 11:28:22 UTC
Partuza documentation needs update
I followed the Partuza installation guide on:
http://www.chabotc.com/guides/partuza_install/
Under "Setting up Shindig for Partuza" it says:
" you need to copy the files you want to use to one of it's directories
it scans for PHP classes (i always prefer the shindig\php\src\socialdata
directory since it makes the most sense),"
However, there is currently no such directory.
Later it says:
"First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
but there are 4 PHP files there.
Later it says:
"edit shindig's configuration by opening the
c:\wamp\www\shindig\php\config.php file"
but currently the configuration is in
c:\wamp\www\shindig\php\config\local.php.
Later it says:
"And change the *'handlers' => ''* configuration to read *'handlers' =>
'PartuzaHandler',"
but currently there are other configuration options to use:
'people_service' => 'PartuzaPeopleService',
'activity_service' => '**Partuza**ActivitiesService',
'app_data_service' => '**Partuza**AppDataService',
'messages_service' => '**Partuza**MessagesService',
*
Re: Partuza documentation needs update
Posted by Erel Segal <er...@gmail.com>.
I suggest adding a sentence after "we need to create a new virtual host in
the httpd-vhosts.conf file":
"Look at your httpd.conf file and make sure the line "Include
conf/extra/httpd-vhosts.conf" is not commented".
(This would have saved me some hours of frustration...)
2008/8/15, Erel Segal <er...@gmail.com>:
>
> I meant a human installer, not a script :)
>
> 2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>>
>> Ah, well you could have mentioned that your plan also included creating an
>> installer, since you originally wrote about 'svn', which isn't quite an
>> installer :)
>>
>> Having an installer sounds great though, as the open source meme goes:
>> "Patches are welcome"
>>
>>
>> On Aug 14, 2008, at 12:04 PM, Erel Segal wrote:
>>
>> Of course Shindig should not depend on Partuza. What I meant is that,
>>> when
>>> first installing Partuza, the installer can create a "local.php" file
>>> under
>>> shindig/php/config, that will read a configuration file in Partuza's
>>> tree.
>>> Later, when Partuza is updated and the configuration is changed, there
>>> will
>>> be no need to change shindig's configuration file.
>>>
>>>
>>> 2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>>>
>>>>
>>>> Hey Erel,
>>>>
>>>> Your completely right on the need of those docs being updated, time has
>>>> been a bit short but i'll make sure i'll get around to it this week, a
>>>> few
>>>> people hit that snag already.
>>>>
>>>> However Shindig and Partuza are completely separate projects, so making
>>>> Shindig depends on partuza being present (or even if that wasn't the
>>>> case,
>>>> making anything depend on partuza being on a certain file path) is not
>>>> very
>>>> desirable :)
>>>>
>>>> -- Chris
>>>>
>>>>
>>>> On Aug 14, 2008, at 11:33 AM, Erel Segal wrote:
>>>>
>>>> P.S. maybe it would be easier to put the "local.php" configuration file
>>>> in
>>>>
>>>>> the Partuza SVN tree, and put the following content in
>>>>> shindig/php/config/local.php:
>>>>>
>>>>> <?php
>>>>> require(dirname(__FILE__).'/../../../partuza/local.php');
>>>>> ?>
>>>>>
>>>>> It is more natural to put Partuza's configuration in Partuza's svn tree
>>>>> -
>>>>> this way it will be automatically updated when Partuza is changed.
>>>>>
>>>>>
>>>>>
>>>>> 2008/8/14, Erel Segal <er...@gmail.com>:
>>>>>
>>>>>
>>>>>> I followed the Partuza installation guide on:
>>>>>> http://www.chabotc.com/guides/partuza_install/
>>>>>>
>>>>>> Under "Setting up Shindig for Partuza" it says:
>>>>>> " you need to copy the files you want to use to one of it's
>>>>>> directories
>>>>>> it scans for PHP classes (i always prefer the
>>>>>> shindig\php\src\socialdata
>>>>>> directory since it makes the most sense),"
>>>>>> However, there is currently no such directory.
>>>>>>
>>>>>> Later it says:
>>>>>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>>>>>> but there are 4 PHP files there.
>>>>>>
>>>>>> Later it says:
>>>>>> "edit shindig's configuration by opening the
>>>>>> c:\wamp\www\shindig\php\config.php file"
>>>>>> but currently the configuration is in
>>>>>> c:\wamp\www\shindig\php\config\local.php.
>>>>>>
>>>>>> Later it says:
>>>>>> "And change the *'handlers' => ''* configuration to read *'handlers'
>>>>>> =>
>>>>>> 'PartuzaHandler',"
>>>>>> but currently there are other configuration options to use:
>>>>>> 'people_service' => 'PartuzaPeopleService',
>>>>>>
>>>>>> 'activity_service' => '**Partuza**ActivitiesService',
>>>>>> 'app_data_service' => '**Partuza**AppDataService',
>>>>>> 'messages_service' => '**Partuza**MessagesService',
>>>>>>
>>>>>>
>>>>>> *
>>>>>>
>>>>>>
>>>>>>
>>>>
>>
>
Re: Partuza documentation needs update
Posted by Erel Segal <er...@gmail.com>.
I meant a human installer, not a script :)
2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>
> Ah, well you could have mentioned that your plan also included creating an
> installer, since you originally wrote about 'svn', which isn't quite an
> installer :)
>
> Having an installer sounds great though, as the open source meme goes:
> "Patches are welcome"
>
>
> On Aug 14, 2008, at 12:04 PM, Erel Segal wrote:
>
> Of course Shindig should not depend on Partuza. What I meant is that, when
>> first installing Partuza, the installer can create a "local.php" file
>> under
>> shindig/php/config, that will read a configuration file in Partuza's tree.
>> Later, when Partuza is updated and the configuration is changed, there
>> will
>> be no need to change shindig's configuration file.
>>
>>
>> 2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>>
>>>
>>> Hey Erel,
>>>
>>> Your completely right on the need of those docs being updated, time has
>>> been a bit short but i'll make sure i'll get around to it this week, a
>>> few
>>> people hit that snag already.
>>>
>>> However Shindig and Partuza are completely separate projects, so making
>>> Shindig depends on partuza being present (or even if that wasn't the
>>> case,
>>> making anything depend on partuza being on a certain file path) is not
>>> very
>>> desirable :)
>>>
>>> -- Chris
>>>
>>>
>>> On Aug 14, 2008, at 11:33 AM, Erel Segal wrote:
>>>
>>> P.S. maybe it would be easier to put the "local.php" configuration file
>>> in
>>>
>>>> the Partuza SVN tree, and put the following content in
>>>> shindig/php/config/local.php:
>>>>
>>>> <?php
>>>> require(dirname(__FILE__).'/../../../partuza/local.php');
>>>> ?>
>>>>
>>>> It is more natural to put Partuza's configuration in Partuza's svn tree
>>>> -
>>>> this way it will be automatically updated when Partuza is changed.
>>>>
>>>>
>>>>
>>>> 2008/8/14, Erel Segal <er...@gmail.com>:
>>>>
>>>>
>>>>> I followed the Partuza installation guide on:
>>>>> http://www.chabotc.com/guides/partuza_install/
>>>>>
>>>>> Under "Setting up Shindig for Partuza" it says:
>>>>> " you need to copy the files you want to use to one of it's directories
>>>>> it scans for PHP classes (i always prefer the
>>>>> shindig\php\src\socialdata
>>>>> directory since it makes the most sense),"
>>>>> However, there is currently no such directory.
>>>>>
>>>>> Later it says:
>>>>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>>>>> but there are 4 PHP files there.
>>>>>
>>>>> Later it says:
>>>>> "edit shindig's configuration by opening the
>>>>> c:\wamp\www\shindig\php\config.php file"
>>>>> but currently the configuration is in
>>>>> c:\wamp\www\shindig\php\config\local.php.
>>>>>
>>>>> Later it says:
>>>>> "And change the *'handlers' => ''* configuration to read *'handlers' =>
>>>>> 'PartuzaHandler',"
>>>>> but currently there are other configuration options to use:
>>>>> 'people_service' => 'PartuzaPeopleService',
>>>>>
>>>>> 'activity_service' => '**Partuza**ActivitiesService',
>>>>> 'app_data_service' => '**Partuza**AppDataService',
>>>>> 'messages_service' => '**Partuza**MessagesService',
>>>>>
>>>>>
>>>>> *
>>>>>
>>>>>
>>>>>
>>>
>
Re: Partuza documentation needs update
Posted by Chris Chabot <ch...@xs4all.nl>.
Ah, well you could have mentioned that your plan also included
creating an installer, since you originally wrote about 'svn', which
isn't quite an installer :)
Having an installer sounds great though, as the open source meme goes:
"Patches are welcome"
On Aug 14, 2008, at 12:04 PM, Erel Segal wrote:
> Of course Shindig should not depend on Partuza. What I meant is
> that, when
> first installing Partuza, the installer can create a "local.php"
> file under
> shindig/php/config, that will read a configuration file in Partuza's
> tree.
> Later, when Partuza is updated and the configuration is changed,
> there will
> be no need to change shindig's configuration file.
>
>
> 2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>>
>> Hey Erel,
>>
>> Your completely right on the need of those docs being updated, time
>> has
>> been a bit short but i'll make sure i'll get around to it this
>> week, a few
>> people hit that snag already.
>>
>> However Shindig and Partuza are completely separate projects, so
>> making
>> Shindig depends on partuza being present (or even if that wasn't
>> the case,
>> making anything depend on partuza being on a certain file path) is
>> not very
>> desirable :)
>>
>> -- Chris
>>
>>
>> On Aug 14, 2008, at 11:33 AM, Erel Segal wrote:
>>
>> P.S. maybe it would be easier to put the "local.php" configuration
>> file in
>>> the Partuza SVN tree, and put the following content in
>>> shindig/php/config/local.php:
>>>
>>> <?php
>>> require(dirname(__FILE__).'/../../../partuza/local.php');
>>> ?>
>>>
>>> It is more natural to put Partuza's configuration in Partuza's svn
>>> tree -
>>> this way it will be automatically updated when Partuza is changed.
>>>
>>>
>>>
>>> 2008/8/14, Erel Segal <er...@gmail.com>:
>>>
>>>>
>>>> I followed the Partuza installation guide on:
>>>> http://www.chabotc.com/guides/partuza_install/
>>>>
>>>> Under "Setting up Shindig for Partuza" it says:
>>>> " you need to copy the files you want to use to one of it's
>>>> directories
>>>> it scans for PHP classes (i always prefer the shindig\php\src
>>>> \socialdata
>>>> directory since it makes the most sense),"
>>>> However, there is currently no such directory.
>>>>
>>>> Later it says:
>>>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>>>> but there are 4 PHP files there.
>>>>
>>>> Later it says:
>>>> "edit shindig's configuration by opening the
>>>> c:\wamp\www\shindig\php\config.php file"
>>>> but currently the configuration is in
>>>> c:\wamp\www\shindig\php\config\local.php.
>>>>
>>>> Later it says:
>>>> "And change the *'handlers' => ''* configuration to read
>>>> *'handlers' =>
>>>> 'PartuzaHandler',"
>>>> but currently there are other configuration options to use:
>>>> 'people_service' => 'PartuzaPeopleService',
>>>>
>>>> 'activity_service' => '**Partuza**ActivitiesService',
>>>> 'app_data_service' => '**Partuza**AppDataService',
>>>> 'messages_service' => '**Partuza**MessagesService',
>>>>
>>>>
>>>> *
>>>>
>>>>
>>
Re: Partuza documentation needs update
Posted by Erel Segal <er...@gmail.com>.
Of course Shindig should not depend on Partuza. What I meant is that, when
first installing Partuza, the installer can create a "local.php" file under
shindig/php/config, that will read a configuration file in Partuza's tree.
Later, when Partuza is updated and the configuration is changed, there will
be no need to change shindig's configuration file.
2008/8/14, Chris Chabot <ch...@xs4all.nl>:
>
> Hey Erel,
>
> Your completely right on the need of those docs being updated, time has
> been a bit short but i'll make sure i'll get around to it this week, a few
> people hit that snag already.
>
> However Shindig and Partuza are completely separate projects, so making
> Shindig depends on partuza being present (or even if that wasn't the case,
> making anything depend on partuza being on a certain file path) is not very
> desirable :)
>
> -- Chris
>
>
> On Aug 14, 2008, at 11:33 AM, Erel Segal wrote:
>
> P.S. maybe it would be easier to put the "local.php" configuration file in
>> the Partuza SVN tree, and put the following content in
>> shindig/php/config/local.php:
>>
>> <?php
>> require(dirname(__FILE__).'/../../../partuza/local.php');
>> ?>
>>
>> It is more natural to put Partuza's configuration in Partuza's svn tree -
>> this way it will be automatically updated when Partuza is changed.
>>
>>
>>
>> 2008/8/14, Erel Segal <er...@gmail.com>:
>>
>>>
>>> I followed the Partuza installation guide on:
>>> http://www.chabotc.com/guides/partuza_install/
>>>
>>> Under "Setting up Shindig for Partuza" it says:
>>> " you need to copy the files you want to use to one of it's directories
>>> it scans for PHP classes (i always prefer the shindig\php\src\socialdata
>>> directory since it makes the most sense),"
>>> However, there is currently no such directory.
>>>
>>> Later it says:
>>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>>> but there are 4 PHP files there.
>>>
>>> Later it says:
>>> "edit shindig's configuration by opening the
>>> c:\wamp\www\shindig\php\config.php file"
>>> but currently the configuration is in
>>> c:\wamp\www\shindig\php\config\local.php.
>>>
>>> Later it says:
>>> "And change the *'handlers' => ''* configuration to read *'handlers' =>
>>> 'PartuzaHandler',"
>>> but currently there are other configuration options to use:
>>> 'people_service' => 'PartuzaPeopleService',
>>>
>>> 'activity_service' => '**Partuza**ActivitiesService',
>>> 'app_data_service' => '**Partuza**AppDataService',
>>> 'messages_service' => '**Partuza**MessagesService',
>>>
>>>
>>> *
>>>
>>>
>
Re: Partuza documentation needs update
Posted by Chris Chabot <ch...@xs4all.nl>.
Hey Erel,
Your completely right on the need of those docs being updated, time
has been a bit short but i'll make sure i'll get around to it this
week, a few people hit that snag already.
However Shindig and Partuza are completely separate projects, so
making Shindig depends on partuza being present (or even if that
wasn't the case, making anything depend on partuza being on a certain
file path) is not very desirable :)
-- Chris
On Aug 14, 2008, at 11:33 AM, Erel Segal wrote:
> P.S. maybe it would be easier to put the "local.php" configuration
> file in
> the Partuza SVN tree, and put the following content in
> shindig/php/config/local.php:
>
> <?php
> require(dirname(__FILE__).'/../../../partuza/local.php');
> ?>
>
> It is more natural to put Partuza's configuration in Partuza's svn
> tree -
> this way it will be automatically updated when Partuza is changed.
>
>
>
> 2008/8/14, Erel Segal <er...@gmail.com>:
>>
>> I followed the Partuza installation guide on:
>> http://www.chabotc.com/guides/partuza_install/
>>
>> Under "Setting up Shindig for Partuza" it says:
>> " you need to copy the files you want to use to one of it's
>> directories
>> it scans for PHP classes (i always prefer the shindig\php\src
>> \socialdata
>> directory since it makes the most sense),"
>> However, there is currently no such directory.
>>
>> Later it says:
>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>> but there are 4 PHP files there.
>>
>> Later it says:
>> "edit shindig's configuration by opening the
>> c:\wamp\www\shindig\php\config.php file"
>> but currently the configuration is in
>> c:\wamp\www\shindig\php\config\local.php.
>>
>> Later it says:
>> "And change the *'handlers' => ''* configuration to read
>> *'handlers' =>
>> 'PartuzaHandler',"
>> but currently there are other configuration options to use:
>> 'people_service' => 'PartuzaPeopleService',
>> 'activity_service' => '**Partuza**ActivitiesService',
>> 'app_data_service' => '**Partuza**AppDataService',
>> 'messages_service' => '**Partuza**MessagesService',
>>
>>
>> *
>>
Re: Partuza documentation needs update
Posted by Erel Segal <er...@gmail.com>.
Also, in this case, you can put in that configuration file the following
option:
'extension_class_paths' => dirname(__FILE__).'/Shindig',
this way, you don't need to copy the PHP files from c:\wamp\www\partuza\Shindig
to the shindig tree - this should make the installation easier.
2008/8/14, Erel Segal <er...@gmail.com>:
>
> P.S. maybe it would be easier to put the "local.php" configuration file in
> the Partuza SVN tree, and put the following content in
> shindig/php/config/local.php:
>
> <?php
> require(dirname(__FILE__).'/../../../partuza/local.php');
> ?>
>
> It is more natural to put Partuza's configuration in Partuza's svn tree -
> this way it will be automatically updated when Partuza is changed.
>
>
>
> 2008/8/14, Erel Segal <er...@gmail.com>:
>>
>> I followed the Partuza installation guide on:
>> http://www.chabotc.com/guides/partuza_install/
>>
>> Under "Setting up Shindig for Partuza" it says:
>> " you need to copy the files you want to use to one of it's directories
>> it scans for PHP classes (i always prefer the shindig\php\src\socialdata
>> directory since it makes the most sense),"
>> However, there is currently no such directory.
>>
>> Later it says:
>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>> but there are 4 PHP files there.
>>
>> Later it says:
>> "edit shindig's configuration by opening the
>> c:\wamp\www\shindig\php\config.php file"
>> but currently the configuration is in
>> c:\wamp\www\shindig\php\config\local.php.
>>
>> Later it says:
>> "And change the *'handlers' => ''* configuration to read *'handlers' =>
>> 'PartuzaHandler',"
>> but currently there are other configuration options to use:
>> 'people_service' => 'PartuzaPeopleService',
>> 'activity_service' => '**Partuza**ActivitiesService',
>> 'app_data_service' => '**Partuza**AppDataService',
>> 'messages_service' => '**Partuza**MessagesService',
>>
>>
>> *
>>
>
>
Re: Partuza documentation needs update
Posted by Erel Segal <er...@gmail.com>.
P.S. maybe it would be easier to put the "local.php" configuration file in
the Partuza SVN tree, and put the following content in
shindig/php/config/local.php:
<?php
require(dirname(__FILE__).'/../../../partuza/local.php');
?>
It is more natural to put Partuza's configuration in Partuza's svn tree -
this way it will be automatically updated when Partuza is changed.
2008/8/14, Erel Segal <er...@gmail.com>:
>
> I followed the Partuza installation guide on:
> http://www.chabotc.com/guides/partuza_install/
>
> Under "Setting up Shindig for Partuza" it says:
> " you need to copy the files you want to use to one of it's directories
> it scans for PHP classes (i always prefer the shindig\php\src\socialdata
> directory since it makes the most sense),"
> However, there is currently no such directory.
>
> Later it says:
> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
> but there are 4 PHP files there.
>
> Later it says:
> "edit shindig's configuration by opening the
> c:\wamp\www\shindig\php\config.php file"
> but currently the configuration is in
> c:\wamp\www\shindig\php\config\local.php.
>
> Later it says:
> "And change the *'handlers' => ''* configuration to read *'handlers' =>
> 'PartuzaHandler',"
> but currently there are other configuration options to use:
> 'people_service' => 'PartuzaPeopleService',
> 'activity_service' => '**Partuza**ActivitiesService',
> 'app_data_service' => '**Partuza**AppDataService',
> 'messages_service' => '**Partuza**MessagesService',
>
>
> *
>