Summary
In some cases you may want to consolidate many small / low resource sites onto a single VM. It is possible to increase the resources that are used by a single VM making it cheaper to have a single larger VM than multiple smaller VMs.
Recommended Software
Name |
Version |
---|---|
PHP |
5.4.x |
php_apc |
3.1.x |
php_imagick |
3.1.0 |
mysql |
5.5.x |
Optional Software
Name |
Version |
---|---|
Python* |
2.7.x |
Coldfusion** |
10 |
Ruby |
1.9.3 |
Tends to not work well under "Shared Apache" you may need to create a few "Standalone Apache" instances for Python sites/applications. Coldfusion consumes a large amount of resources so you may want to combine multiple sites under a single instance or expand the amount of CPU/Memory on the VM.
VMs / Instances / Vhosts
The number of VMs will depend on how comfortable you are with putting multiple sites/applications together. You should group by technology/department/focus, etc...
In a multi-tenant environment using "Shared Apache" will allow you to consolidate many sites together. You should take particular care to avoid allowing sites to run as the "lamp" user since this user can access all sites! The sites should run as "lampuserXXX".
In the following you can see that a site can have a dev/test/prod and/or run multiple subsites under a single instance.
Name |
Purpose |
Instance |
Vanity URL |
Comments |
---|---|---|---|---|
webhostXXX |
site1 |
[site1] |
[site1].[subdomain].cornell.edu |
production |
webhostXXX |
site1 |
[site1] |
[site1]dev.[subdomain].cornell.edu |
dev for site1 |
webhostXXX |
site2 |
[site2] |
[site2].[subdomain].cornell.edu |
production site, no dev! |
webhostXXX |
site3 |
[site3] |
[group1].[site3].[subdomain].cornell.edu |
subsite |
webhostXXX |
site3 |
[site3] |
[group2].[site3].[subdomain].cornell.edu |
subsite |
webhostXXX |
site3 |
[site3] |
[group3].[site3].[subdomain].cornell.edu |
subsite |