| 75 | | PHP is working as module for webserver. |
| | 75 | PHP is working as module for webserver. This most common and simple setup. You can check phpinfo() to see if you have this setup: |
| | 76 | |
| | 77 | [[Image(hssr-php-1-dso.jpg)]] |
| | 78 | |
| | 79 | This setup works fast because web-server don't need to load PHP interpreter each time, it works as part of web-server. You can even speedup it by installing opcode cache extensions for PHP, we recommend [http://eaccelerator.net/ eAccelerator], because you can get advantage of shared memory cache which offer eAccelerator since Dolphin 7.0.3. |
| | 80 | |
| | 81 | The problem maybe on shared hosting, because PHP scripts are executing under the same web-user (nobody or apache as usual) and one account owner can get access to nobody files of other account on the server, but it can be properly configured with correct "base_path" restriction to disable such access from PHP script. If you have VPS or dedicated server this is not a problem, since all sites on the server are yours. |
| | 82 | |
| | 83 | This setup considered to be secured, because of in case of the hacking attempt it is possible to upload files to nobody directory only and modify nobody files only, no risk to overwrite or modify index.php file for example (if it has correct permissions) |
| | 84 | |
| | 85 | '''Advantages:''' |
| | 86 | * speed |
| | 87 | * security |
| | 88 | * easy install |
| | 89 | * opcode cache extensions support |
| | 90 | |
| | 91 | |
| | 92 | '''Disadvantages:''' |
| | 93 | * maybe insecure on shared hosting |
| | 94 | |
| | 95 | '''Conclusion:''' if you already have such setup it is ok to leave it, but consider to install opcode cache extension. |
