Centralized Code for Hosted Solution
Posted: Fri Aug 11, 2006 4:02 pm
Hi,
We've built a substantial code engine for our upcoming hosted solution. What we would like to do is centralize this code base in one place, and access it from there from each customer account.
Since the engine itself is large, and will grow increasingly large, it doesn't make sense to have it installed on each account, as any upgrades will exponentially grow our storage overhead.
How is the best way to centralize this codebase? Everything will be accessed from our owned servers under our control, and our customers will not have FTP access. So there's not an issue of remotely including it from a location out of our control.
We've thought about giving every account root access and pointing at the codebase in the root folder of the servers, but that seems like a HUGE security risk to take, especially with sensitive data. We've thought about SOAP calls to a SOAP server as well, but that seems like overkill.
There's only one file that needs to be included, and that file takes care of loading the rest of the engine, and including the other files necessary.
Thanks,
Josh
We've built a substantial code engine for our upcoming hosted solution. What we would like to do is centralize this code base in one place, and access it from there from each customer account.
Since the engine itself is large, and will grow increasingly large, it doesn't make sense to have it installed on each account, as any upgrades will exponentially grow our storage overhead.
How is the best way to centralize this codebase? Everything will be accessed from our owned servers under our control, and our customers will not have FTP access. So there's not an issue of remotely including it from a location out of our control.
We've thought about giving every account root access and pointing at the codebase in the root folder of the servers, but that seems like a HUGE security risk to take, especially with sensitive data. We've thought about SOAP calls to a SOAP server as well, but that seems like overkill.
There's only one file that needs to be included, and that file takes care of loading the rest of the engine, and including the other files necessary.
Thanks,
Josh