Hi Edwin,

I would like to seek for your advice if I want to establish a testing JMS site and a production JMS site.

As more and more slave sites will be deployed on JMS, I want to do all development and testing on Testing JMS site only. After the development is completed then move to the production JMS site.

While we can use some tools to sync files between the testing and the production JMS, it seems no easy way to sync database files between testing and production JMS site.

Do you have any recommendation?

Many thanks.

Seth

All depends if your websites register the users or not.
If this is just informational website, you can easily create several slave site that are clone of an existing website and only change the domain name in the slave site to activate a specific website at a given time.
You could create slave_v1 with www.domain.com and prepare a slave_v2 with dev.domain.com.
Once it is OK, you can disable the slave_v1 (status = cancel) and use slave_v2 with domain = www.domain.com

If you have also to manage the user, perhaps you could use the JMS 1.2.x feature that allow sharing the user.
In this case, you could split the users and the data into separated websites.
This could give you the opportunity to switch from one website to another one more easily.

This is a very good suggestion!

How about an user at the production site submits some content during the development, eg submit an article, shop something or make an event registration,........

Can this situation be handled in your suggested testing/production model?

Many thanks,

Seth

All depends what you expect to change in development and what you could decide to be "shared" and not modified in development.

If your development just concern the layout, templates, create new menu, enable modules, .... you can try to split the website into its contents that could be partially share and in the layout that could be modified in development.

You could try only share the data like articles or some extensions to benefit of the modification performed in production.

You can also decide to "backup" / "restore" the production website to put it into another place to just test the new development.
In this case, this may be more difficult to synchronize the data later.