I'm building a web application that I'm offering as a hosted solution... so someone would point their domain to my server and pay me some money each month and they would get to use this application on their domain. So I see 3 plausible ways to set this up on my server (just a shared hosting account).
1) Each domain has its own root directory with its own files and each domain gets its own database. This would keep everything separate but would be difficult to make updates since i'll have many instances of the application
2) All the domains would point to the same root directory and use the same actual files, but each domain would get its own database. That would make updates easier and keep all the actual data for site separate.
3) All the domains point to the same root directory and use the same actual files and they all share one database.
Would there be a performance drop if all the sites are using the same files? Anyone have any thoughts or advise? Thanks
1) Each domain has its own root directory with its own files and each domain gets its own database. This would keep everything separate but would be difficult to make updates since i'll have many instances of the application
2) All the domains would point to the same root directory and use the same actual files, but each domain would get its own database. That would make updates easier and keep all the actual data for site separate.
3) All the domains point to the same root directory and use the same actual files and they all share one database.
Would there be a performance drop if all the sites are using the same files? Anyone have any thoughts or advise? Thanks