CiviCRM Community Forums (archive)

Updates:

I am posting my project updates,

Last week accomplishments/problems faced:
-After using civix in windows environment I was facing some issues regarding calling civix under CMS root directory, after vigorous discussion on IRC with Eileen and with responses from community on this thread, we narrowed down to the conclusion.
-I tried Vagrant, (Linux based OS virtualization) which is primarily used to sharing Linux environment and modified files with windows. Then after few more discussions with Joe McLaughlin and Joe Murray on forum thread, switching the OS to Linux (Ubuntu/Fedora) was advised.
-I already have dual boot machine with Ubuntu 14.04 LTS installed, So I read documentation about civicrm-buildkit and CLI tools on github which are related to installation on Linux.

Target for coming week:
After checkin meeting on Skype (15/5 07:30am IST) with the team, goals and this week's target are drawn along with some exercises and activities like :
-Installing up and running drupal CMS along with latest CiviCRM version on localhost (Apache server, MySQL already installed).
-PhpStorm (PHP IDE) will be installed along with Xdebug which will be used for debugging.
-After installation tasks : will try exercises recommended by Joe McLaughlin on https://github.com/ginkgostreet/com.ginkgostreet.devtraining
-developing a wrapper to get API for contact in accordance with OSDI format.
-trying and experimenting with HAL browser on https://github.com/mikekelly/hal-browser
-making offline availability of HAL browser which will be accessible from localhost using Apache.

Further, I will be making use of OSDI Implementation wiki page (http://wiki.civicrm.org/confluence/display/CRM/OSDI+Integration) on which I will be posting and maintaining record of meeting minutes and track discussion. I will post records of previous introduction meetings on Skype as well along with prime aspects, vital implementation information and profiles about OSDI and technological guidance received from attending weekly OSDI Tech calls on Lucid meetings.
Also I would definitely like to see some mentor invocation about the tasks mentioned above or any additional exercises or activity they want to add up which can be different from the current target.

Thank you.

Hi,

I have a working dev environment setup on Linux, installed civix as well. My primary concern is about how I can configure civix to look into correct CMS directory containing civicrm configuration file so as to get over unable to locate CMS root exception.
I came across this issue on github :
https://github.com/totten/civix/issues/45

I tried some modifications on the "ClientFactory.php" present in civix/src/CRM/ClientBundle of the civix package (made URL edits in relPaths array) but I think it requires configurations to be made elsewhere or a certainly different approach.
I am eagerly awaiting for responses from the community.
Thank you.

Anudit - wanna sort this out on IRC?

Heh Anudit - Eileen should be able to sort you out on IRC in a way that avoids you needing to do special work to get civix to find the CMS or use factory pattern.

Looks like I missed you by 3 hours!

Yes Eileen, definitely we should catch up with a plan. I was about to pm you regarding deciding suitable timings for us to communicate properly. Though I keep hanging around in IRC. So please provide me with best timings possible according to you, I'll manage my schedule accordingly.
Thanks.

Updates:

After discussing the issue with Eileen on IRC we came across that I was having some problems with my civicrm-buildkit which was not properly git-cloned into the correct directory. Then after following the tutorial on installing civicrm-buildkit from https://buildkit.civicrm.org/#/tutorials few hurdles came along:

1. While executing the command 'civi-download-tools" for downloading and installing the civicrm-buildkit which gave an error 'node : command not found' which was required for installing CiviCRM 4.6+ but I had installed Node.js before, so the problem here was that 'node' was not a recognized command on Ubuntu rather it worked fine when I called nodejs. To overcome this problem to continue with the automated process of installation which can be solved by these ways:

• Edit ~/.bashrc and make alias of nodejs as node by adding : (but the problems can come with automated installations)

alias node=nodejs

• Install nodejs-legacy with apt-get (worked perfectly fine )

sudo apt-get install nodejs-legacy

2. Second problem I came across was while running 'amp test' for checking the configurations made in 'amp config'. I suppose I have correctly configured amp but unfortunately I am getting this error :
Create test application
Create data directory: /home/anudit/.amp/canary/data/cRtGZ0pP8CQlCrUgo5bbMWsXBCDPm6ep
AMP_URL='http://localhost:7979'
AMP_ROOT='/home/anudit/.amp/canary'
AMP_DB_DSN='mysql://canary_u4ntd:rfKrDtbMfsbxlM80@127.0.0.1:3306/canary_u4ntd?new_link=true'
AMP_DB_USER='canary_u4ntd'
AMP_DB_PASS='rfKrDtbMfsbxlM80'
AMP_DB_HOST='127.0.0.1'
AMP_DB_PORT='3306'
AMP_DB_NAME='canary_u4ntd'
AMP_DB_ARGS='-h 127.0.0.1 -u canary_u4ntd -prfKrDtbMfsbxlM80 -P 3306 canary_u4ntd'

Connect to test application
Expect response: "response-code-VrkPjPnUCy"
PHP Warning:  file_get_contents(http://localhost:7979/index.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden
 in /opt/buildkit/vendor/totten/amp/src/Amp/Command/TestCommand.php on line 153

Warning: file_get_contents(http://localhost:7979/index.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden
 in /opt/buildkit/vendor/totten/amp/src/Amp/Command/TestCommand.php on line 153
Received incorrect response: ""
Tip: Try running "amp config" and/or restarting the webserver.

Could anyone provide any leads on this, how can I get over with this error ? so I can proceed further with civibuild
Eagerly waiting for the responses from the community.
Thank you.

I note this message

"Please pay attention to amp config and amp test. They may ask you to perform some setup tasks (such as editing the Apache configuration and restarting Apache). amp test should succeed before continuing. "

So - re-running amp config may give you the message if you are missing it