Hi, im in the process of moving servers and was wondering if it was possible to run the same zen cart store on two different servers, or if one would work and the other wouldn't?
Thanks
Hi, im in the process of moving servers and was wondering if it was possible to run the same zen cart store on two different servers, or if one would work and the other wouldn't?
Thanks
Yes, you can run the same cart (files and database) on two different servers. However, you can only point DNS to one location. So one of your stores would be at www.yourdomain.com, where the other one would need to be accessed at your server's IP address (or even by using a different domain name). This is very helpful when creating a "test" cart on a new server, without launching the new site til you're ready. Just make sure you change the necessary settings in your configure.php file to handle the URL change.
Not true.
If you do a DNS lookup for google.com (as an example) you'll see that it resolves to no less than eleven different hosts/IPaddresses.
This is not a new technique, it has been used as a form of load balancing for several decades.
The difficult part in regards to using this for ZenCart (and other eCommerce sites) is in keeping the data on the different sites syncronised.
Or by having one site at www.yourdomain.com, and the other at yourdomain.com (without the 'www'). :)
Cheers
Rod
Last edited by RodG; 13 Jun 2012 at 01:22 AM.
I believe kdipaolo is not asking how to spread resources amongst several different servers in a cloud, but rather if they can re-install & test their site on a new server, without disturbing/affecting the original website. The answer is yes, you can, but update configure.php so your "new" site is using the correct URL. The best way to do that is to simply use the new server's IP address. DNS should NOT be changed until they are ready to launch the new website.
I would not recommend changing the main A Record - some users (myself included) don't always type the www. You leave your "new" site vulnerable to unwanted snooping while you are still developing/testing it. Now you will have a serious issue trying to sync data between the two sites. I think you should leave DNS alone until you are ready to make the hosting/server switch.
There are also complications with Google seeing two different copies of the website... use an IP address until launch day, so you don't mess up your search engine rankings and/or make your new site visible to the public before you are ready to do so.
I wasn't looking for an arguement/discussion. I was merely correcting your misinformation in regards to DNS to help prevent further propagation of same.
Rgds
Rod
Me neither, just trying to clear it up so kdipaolo can make a fully informed decision. I think for these purposes my original statement is correct, and it is the simplest way to go about the move.