It creates an environment of pre-production (for an editorial group work, develloppement or otherwise) prior to publication production. This solution allows you to clone the site easily by keeping all the different configurations
You can have a mirror while managing exceptions (file, file, table) and can be used to re-install a site in minutes after haking.
The system uses "rsync" available on all servers linux in general (even on shared hosting like to OVH for example).
The setup is simple for synchronise the websites:
Site master to site slave, without exception,
Database master to database slave, depending on the action plan for each table.
Replication is the only component Joomla (currently) to do this.
I never encounter this problem.
Have you always the problem ?
if so, can you tell me a little more and contact me directly on my website
A real pity as it looks very promising
I just repeat the test personally.
I registered, I confirm that registration, and I download the component after accepting the license.
I had no problem, and I perform the operation in 2 minutes.
I do not understand your problem, you're on your mail?
Would be interesting to have the possibility to start the replication from a menu of automatically every time a form gets submitted.
Unfortunately my programming knowledge is not sufficient to do it myself....
For the rest, perfect tool! Thx!
I would rate it Excellent if it had an option to define the B site configuration.php file settings on the fly. ie.
Temp and log file paths.
And ofcourse the most important one, Database name and user credentials.
to define the configuration of site "B", simply replicate the file configuration.php Site "A" and connect to admin the site "B".
but beware, do not forget to return the file configuration.php in exclusion before the next replication site "A"
Would be nice to see it build and save a new configuration file based on variables set in the settings. I will try to find some time and see if I can submit that to the owner.
Great Job on the Component!
you can replicate all the web / base first, then change the configuration of the site (slave site) in the administration of joomla, then exclude the configuration.php file the next replication (Web Master), not the delete the new configuration (Web Slave)
But if you have any ideas, thank you for your help
I look forward to the continued development of the great idea.
1 / the configuration file should not be transferred because it has a different setting depending on the site.
- File path
- DB Connect
must indeed transferred by hand the first time or temporarily remove exceptions Replication file (component / replication / preference), then re-setting according to the second configuration
2 / white screen comes the problem of re-setting the configuration file of destination.
Note: If you do not manually set the second configuration (destination). something very simple is to install a joomla (same version as the source) in this folder and go to the end of the installation procedure (thus "deleting file installation"), then replicated by above. and there, it works without problem