View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 2 | WADF | Core | public | 14 Jan 2008 11:42 | 28 Jan 2008 22:30 |
| Reporter | timj | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 0.6.2 | ||||
| Summary | 2: Make easy way to add additional elements to PHP include_path | ||||
| Description | WADF should provide (or should it?) an easy way to add elements to the PHP include path on a per-profile basis e.g. on a dev machine to add an additional path for local checkouts of dependencies that need to be modified. | ||||
| Tags | No tags attached. | ||||
|
|
This is fixed in WADF 0.6.2 by means of: a) using the local_config variable to define per-site paths which can be defaulted to empty, and b) Setting a local preferred value in .wadf-instance For example, a php.ini.template may contain: include_path=.:/path/to/library:@php_extra_include_path@:/path/to/something/else The app-specific wadf.conf (i.e. the file pointed to by local_config) may contain: [globals] php_extra_include_path = The .wadf-instance file may then contain something like: ... php_extra_include_path = /my/special/local/path .... |
