[FX.php List] Ongoing saga of FMS 13 and FX.php... still no luck

[BEVERLY VOTH]

When I *had* a corral full of servers, each one had a purpose. MySQL was separate from MS SQL was separate from Web Servers was separate from FMS was separate from Mail Server, etc. Our motto was: "single point of failure: (we had backup and ability to hot-swap drives), but when a machine went down, it didn't take the entire herd. Dale's right. If you want FMS13 & WebDirect, it's going to demand a bunch. So it makes sense to put Web Sites on a Web Server and call the dbs as needed. You can even limit access to the dbs within the same network (IP range, likely), so have added security, too.

Beverly

On 26 Mar 2014, at 10:58 AM, Dale Bengston wrote:

> It seems the best solution is to let FileMaker have its own server and host the web/FX stuff on a separate machine. This is acceptable, but not ideal. Fortunately, web servers don’t have to be super powerful, expensive machines. Hard drive speed and RAM are more important than raw processor speed.
> 
> My last remaining FileMaker client just upgraded to FMS12, so fortunately it’ll be a while before we face down this problem. Maybe FMI will come around.
> 
> Dale