EDIT

This page wants to give help while setting up different development environments.

There may be other places in the wiki with this kind of information. If you find some please move them here.

### Local dataportal development and test environment

1) Install Apache Server 2.2.x

2) Install PHP

2a) Include the path to libmysql.dll (e.g.: C:\Programme\php-5.2.6) into your Path 

2b) Try to run Apache server

3) Insert the following into the appache conf\httpd.conf file(below the LoadModule part at about Line 120) and adapt them accordingly:

      1. PHP modules

  1. php5

LoadModule php5_module "c:/Programme/php-5.2.6/php5apache2_2.dll"

1. configure the path to php.ini

PHPIniDir "c:/Programme/php-5.2.6/"

4) Install PDT (PHP) plugin in elcipse from http://www.eclipse.org/pdt/

5)Give the according rights to the eclipse project within  appache ..\conf\httpd.conf. E.g.:

<Directory "D:/eclipse_workspace/Drupal5">

	AllowOverride All

	Options Indexes

	Order allow,deny

	Allow from all

</Directory>

or use apache only localy by adding:

DocumentRoot "D:/eclipse_workspace/"

5)Add aliases for different projects to appache ..\conf\httpd.conf. E.g.:

    Alias "/drupal_test"     "D:/eclipse_workspace/Drupal5"

    Alias "/expertsdb"       "D:/eclipse_workspace/Drupal5"

    Alias "/drupal_demo"     "D:/eclipse_workspace/Drupal5"

    Alias "/cdm_dataportal"  "D:/eclipse_workspace/Drupal5"

    Alias "/drupal6"         "D:/eclipse_workspace/Drupal6"

6) install jetty server (zipped version) from http://www.mortbay.org/jetty-6/

7) install jetty launcher plugin in eclipse from http://dbpowder.sourceforge.net/etc/jettylauncher6/updates/

   !! There is an old version too on sourceforge, don't use it!!

8) Download php_xdebug-xxx.dll from http://xdebug.org

Move php_xdebug-xxx.dll into your ..\PHP\ext folder

9) Add the following to your php.ini and adapt accordingly:

[xdebug]

zend_extension_ts=C:\Program Files\php-5.2.1\ext\php_xdebug-2.0.1-5.2.1.dll

xdebug.remote_enable=1

xdebug.remote_handler=dbgp

xdebug.remote_mode=req

xdebug.remote_port=9000

xdebug.remote_host=127.0.0.1

xdebug.remote_log=C:\Program Files\Apache Software Foundation\Apache2.2\logs\xdebug_remote.log

xdebug.profiler_enable = 0

xdebug.profiler_enable_trigger = 0

;     Type: integer, Default value: 0

;     When this setting is set to 1, you can trigger the generation of profiler files by using the XDEBUG_PROFILE GET/POST parameter. This will then write the profiler data to defined directory.

xdebug.profiler_output_dir = D:\tmp

; xdebug.profiler_output_name

;     Type: string, Default value: cachegrind.out.%p

;     This setting determines the name of the file that is used to dump traces into. The setting specifies the format with format specifiers, very similar to sprintf() and strftime(). There are several format specifiers that can be used to format the file name.