I have written a shopping cart application customized my clients' nitche industry. The php scripts will be the same for every web site that uses the cart (I host them all). My question is this:
Is it better to install one set of scripts on my server that all sites use, or to install a seperate set of scripts for each virtual account (user)?
I'd like to be able to use a single set of scripts, for easy upgrading, etc., but is there a disadvantage to this method?
Thanks in advance. NOTE: The application is just straight PHP/mySQL.
One script for everyone, or to each his own?
Moderator: General Moderators
In this case, it's definately better to put it on your server and have them use it off your hosting. I built a shopping cart as well for my company, and that is how we host it for all 1200+ of our stations.
It just makes for easier debugging and also for easier management. If you spread those files everywhere, you will have a whole galaxy of issues, mainly having to update the exact same problem on every single machine you put your code on.
It just makes for easier debugging and also for easier management. If you spread those files everywhere, you will have a whole galaxy of issues, mainly having to update the exact same problem on every single machine you put your code on.
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
For me it depends on whether the code is changing very much. If it is very stable then central is better. If it is part of a common application where upgrades will happen to all sites then common is better.
You can also have the both configurations if you have the search path set to "." and then "/path/to/common/libs" because it will find the local copy first if it exists and override the common files.
You can also have the both configurations if you have the search path set to "." and then "/path/to/common/libs" because it will find the local copy first if it exists and override the common files.
(#10850)