Reasoning:
- each instance of apache would run as a different user so that you could better limit access to files through permissions. ie) user1 would not be able to use PHP/Apache to read code within files that he/she would not otherwise be able to read.
- you could still share a global codebase of files with only certain users by applying permissions correctly.
The following link gives a quick breakdown as how this may be possible:
http://www.unitedknowledge.nl/howtos/multiple_apache_instances
Concerns:
- 50 users on a system would mean 50 Instances of apache running.
- How much DRAM does each instance of apache reserve/use?
- Are there other resource concerns?
- I only have 1 server.
- Is there an easier/better way to do this? I am not sure if chroot or jails would accomplish my needs.
Please advise...
- each instance of apache would run as a different user so that you could better limit access to files through permissions. ie) user1 would not be able to use PHP/Apache to read code within files that he/she would not otherwise be able to read.
- you could still share a global codebase of files with only certain users by applying permissions correctly.
The following link gives a quick breakdown as how this may be possible:
http://www.unitedknowledge.nl/howtos/multiple_apache_instances
Concerns:
- 50 users on a system would mean 50 Instances of apache running.
- How much DRAM does each instance of apache reserve/use?
- Are there other resource concerns?
- I only have 1 server.
- Is there an easier/better way to do this? I am not sure if chroot or jails would accomplish my needs.
Please advise...