Changes between Version 4 and Version 5 of faq/drupal/configuration
- Timestamp:
- Sep 28, 2010, 5:24:19 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
faq/drupal/configuration
v4 v5 10 10 11 11 * It means everyone has to use the same DocumentRoot - you cannot, for example, add your own `robots.txt` file or decide you want to customize your `.htaccess` file 12 * It does not work with su PHP- a security mechanism that restricts the permissions of your Drupal installation to just your account. When using multi-site, a vulnerability in one site can be used to do damage to another site on the same server.12 * It does not work with suexec - a security mechanism that restricts the permissions of your Drupal installation to just your account. When using multi-site, a vulnerability in one site can be used to do damage to another site on the same server. 13 13 14 14 In short, the multi-site approach is both restrictive and insecure. … … 16 16 == How does the MF/PL approach work? == 17 17 18 Our approach uses symlinks instead. It is designed to work with su PHP, in which the PHP process running runs with the privileges of the user who owns the file.18 Our approach uses symlinks instead. It is designed to work with suexec, in which the PHP process running runs with the privileges of the user who owns the file. 19 19 20 20 Using our approach, every member has their own web directory, which they control. The web directory contains symlinks to all the top level directories in Drupal core (`includes`, `misc`, etc.) except for the files and sites directories - these are real directories under the control of the user. In addition, each top level file (`index.php`, `cron.php`, etc) is symlinked in the user's web directory, but with the name `index.drupal.php`, `cron.drupal.php`, etc. Finally, every top level file is created and owned by the user with the original Drupal name (`index.php`, `cron.php`) and with a simple one line of php code which includes the Drupal symlink. For example, `index.php` contains: