A PCRE internal error occured. This might be caused by a faulty plugin
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
packages:amp [2013/12/17 10:47] admin [Running Multiple Apache Instances] |
packages:amp [2013/12/17 11:38] (current) admin [Installing Multiple Versions of PHP] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Looking for Flexibility ===== | ===== Looking for Flexibility ===== | ||
| - | Although it is common to use those services, they often are deployed in a way that doesn't offer great flexibility. Specifically the apache configuration as well as the php version that is used by apache are monolithic and do no allow for a great deal of "per virtual host" configuration. | + | Although it is common to use those services, they often are deployed in a way that doesn't offer great flexibility. Specifically the Apache configuration as well as the php version that is used by Apache are monolithic and do no allow for a great deal of "per virtual host" configuration. |
| - | The goal here will be to deploy the AMP base components in such a way that they will allow a greater deal of "per virtual host" configuration options. Basically what we'll aim at doing is run multiple instances of apache with different configuration files, as well as allow "per virtual host" selection of the php version to run. | + | The goal here will be to deploy the AMP base components in such a way that they will allow a greater deal of "per virtual host" configuration options. Basically what we'll aim at doing is run multiple instances of Apache with different configuration files, as well as allow "per virtual host" selection of the php version to run. |
| ===== Running Multiple Apache Instances ===== | ===== Running Multiple Apache Instances ===== | ||
| Line 12: | Line 12: | ||
| What we'd need here is to have separate, lighter, Apache configurations for your mod_perl, mod_python and mod_php apps, listening on different ports (e.g. 81, 82, 83), and have a reverse proxy instance of Apache with virtual hosts configured to pass requests to the corresponding Apache instances. | What we'd need here is to have separate, lighter, Apache configurations for your mod_perl, mod_python and mod_php apps, listening on different ports (e.g. 81, 82, 83), and have a reverse proxy instance of Apache with virtual hosts configured to pass requests to the corresponding Apache instances. | ||
| + | |||
| + | For detailled instructions on how to achieve this, please refer to the [[packages:amp:apache|Apache]] section of the wiki. | ||
| + | |||
| + | ===== Installing Multiple Versions of PHP ===== | ||
| + | One of hard to solve challenges is ensuring that a package do not only run on the specific PHP version the developers have installed on their machines (which often is the latest and greatest, maybe not even released version from SVN), but to cover the whole range of supported PHP versions. | ||
| + | |||
| + | As far as I know, there is no single Linux distribution that supports installing multiple versions of PHP beside each other, we'll have to look for an alternative. A tool to solve all problems with the multiple-php-versions-on-one-machine solution is using [[https://github.com/cweiske/phpfarm|phpfarm]]. | ||
| + | |||
| + | To follow a step by step guide on how to deploy multiple php versions onto your localhost, read the [[packages:amp:php|PHP]] section of the wiki. | ||
| + | |||
| + | ===== Install and Manage MySQL ===== | ||
| + | The last main brick of most standard web development environments is the database management system. Once again here, the established candidate is MySQL, we'll couple it with MySQL Workbench that offers a nice and powerful interface to manage local as well as remote engines. You can follow the installation instructions in the [[packages:amp:mysql|MySQL]] section of the wiki. | ||
