I have only recently come across MySource Matrix after nearly deciding on Drupal or Wordpress for a network of sites and have 90% decided to use MySource Matrix.
We will be developing a number of sites - .com (US audience), .com.au (Aus audience) and .co.uk (UK audience).
We are on a tight budget so initially we want to run everything from a server(s) in Sydney. We will initially use the GPL version.
We want to deploy in a way however that will allow us to make content available directly from the US and UK at a later stage for obvious performance reasons. I am concerned that it would not be easy to export / import MySource sites from one server to a new one (or am I mistaken?) so I am looking at 2 options:
Three instances of MySource Matrix on our initial server (each instance dedicated to .com.au / .com or .co.uk sites) so that when we have servers in US / UK we can just move instances (database and folders) to the new servers.
Single instance running all sites and later setup Squid servers in US / UK to cache content for .com / .co.uk sites. I am not sure how feasable this is. Has anyone used Squid this way internationally?
Can anyone offer any advice on what would be the best option or any other options to consider?
We have not done it with Matrix, but we do it for audio content.
There is an audio origin server located in Wellington, New Zealand. Several Squid proxy servers are located at internet exchanges (Auckland, Wellington and Palo Alto, USA). These all serve content to the public, but they point to origin. All the Squid nodes have the same IP address.
If you do not have a very dynamic site (i.e lots of static content and not many updates) you could probably do this without much problem at all, and set a long cache time.
The other way would be to extract a static version of the site on a daily basis and push that off to your remote servers. (You could use the Git SCM to do this very simply - only changes to content would be pushed to servers saving a lot of bandwidth).
I have only recently come across MySource Matrix after nearly deciding on Drupal or Wordpress for a network of sites and have 90% decided to use MySource Matrix.
We will be developing a number of sites - .com (US audience), .com.au (Aus audience) and .co.uk (UK audience).
We are on a tight budget so initially we want to run everything from a server(s) in Sydney. We will initially use the GPL version.
We want to deploy in a way however that will allow us to make content available directly from the US and UK at a later stage for obvious performance reasons. I am concerned that it would not be easy to export / import MySource sites from one server to a new one (or am I mistaken?) so I am looking at 2 options:
Three instances of MySource Matrix on our initial server (each instance dedicated to .com.au / .com or .co.uk sites) so that when we have servers in US / UK we can just move instances (database and folders) to the new servers.
Single instance running all sites and later setup Squid servers in US / UK to cache content for .com / .co.uk sites. I am not sure how feasable this is. Has anyone used Squid this way internationally?
Can anyone offer any advice on what would be the best option or any other options to consider?
Thanks!
[/quote]
Moving a whole instance of Matrix from one server to another is fairly trivial if you linux sysadmin experience. Especially if the config is identical, including the file paths in use. Moving sites from inside an instance to another might as well be impossible for practical purposes.
You can also do master/slave replication of the database and filesystem (with slony and rsync respectively), which is how we run our website from Cardiff with a hot backup in London, and vice versa with our intranet.
[quote]
Moving a whole instance of Matrix from one server to another is fairly trivial if you linux sysadmin experience. Especially if the config is identical, including the file paths in use. Moving sites from inside an instance to another might as well be impossible for practical purposes.
You can also do master/slave replication of the database and filesystem (with slony and rsync respectively), which is how we run our website from Cardiff with a hot backup in London, and vice versa with our intranet.
[/quote]
I have done a quick setup of 2 instances of Matrix on a single server and it seems to work fine. Are there any problems or issues that I may come across that anyone is aware of such as upgrading etc.?
You can install as many different instances of Matrix as you need on a single server. Just make sure your upgrade them independently. Don't try and share code unless you really know what you are doing and will upgrade them all at once.