Can anyone suggest the config to setup webgrind with Nginx server? about webgrind

[jamwaffles]

What web server package you use is irrelevant, it's the PHP bit that matters. Are you using php5-fpm?

Also this isn't strictly speaking a bug. Try ServerFault or Superuser instead.

[EagleEyeJohn]

WIth Apache, we use a shell file in exec-once folder...

The file .../files/something/site-path.txt contains the basename of the virtualhost root folder (e.g. /var/www/foo -> foo). [If someone can offer a better way of obtaining 'foo', that'd be appreciated]

#!/bin/bash
# MUST use LF not CRLF line endings
# to run again once provisioned, you must execute
# sudo rm /.puphpet-stuff/exec-once-ran

VAGRANT_CORE_FOLDER=$(cat "/.puphpet-stuff/vagrant-core-folder.txt")

MY_SITE=$(cat "${VAGRANT_CORE_FOLDER}"/files/something/site-path.txt)

cd /var/www/"${MY_SITE}"/public_html
pwd
wget https://webgrind.googlecode.com/files/webgrind-release-1.0.zip
unzip webgrind-release-1.0.zip
rm -f webgrind-release-1.0.zip
cd webgrind
pwd
echo "php_flag xdebug.profiler_enable 0" > .htaccess

[eelkevdbos]

1. Install php5-xdebug via sudo apt-get install php5-xdebug
2. Find the php5-fpm xdebug general configuration file, often located at /etc/php5/mods-available/xdebug.ini
3. Edit the file so it looks remotely like this:

zend_extension=xdebug.so
xdebug.remote_enable=1
xdebug.remote_connect_back=1
xdebug.profiler_enable_trigger=1
xdebug.profiler_output_dir=/tmp

1. Restart php5-fpm by executing the command sudo restart php5-fpm

This will enable profiling when triggering it via attachment of the query parameter XDEBUG_PROFILE

The default installation (git clone in /var/www/webgrind) of webgrind will enable webgrind to find the cachegrind files automatically in the temp folder.

[alpha0010]

This appears to be solved. Please re-open if issues persist.