English (United Kingdom)
Jms Multi Site, formerly joomla multisite.
Create, share multiple joomla sites in few clicks !
Message
  • EU e-Privacy Directive

    This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

    View e-Privacy Directive Documents

Welcome, Guest
Please Login or Register.    Lost Password?
Go to bottomPage: 12
TOPIC: Maintence Tab Confusion
#11006
Re:Maintence Tab Confusion 11 Years, 4 Months ago Karma: 54
Concerning your comment with SP, I met a person at JWC12 at San Jose and I told him the same. It seems that SP and the maintenance menu are complementary.

I will try improving things in the next release of JMS (probably a RC2)
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#11007
Re:Maintence Tab Confusion 11 Years, 4 Months ago Karma: 0
Cool, thanks much
djdesjardins
Junior Boarder
Posts: 38
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#11470
Re:Maintence Tab Confusion 10 Years, 10 Months ago Karma: 0
After an additional 6 months of working with the system and some serious sitting and staring through my monitor, I've determined what would help me tremendously in keeping DBs in sync.

Here is the high-level primary use case:

Step 1
    Take a snapshot of the master database
    Update a component(s) in the master
    Take post snapshot of the master DB

Step 2
    Compare snapshots
    Flag changed tables and show differences
    Deselect changed tables that you do not want to update in slaves
    Pre-Generate sql that would sync the tables
    Edit the sql to adjust changes that would be applied to the slaves
    Provide keywords that can populate data from JMS configs & templates, Joomla config, etc

Step 3
    Select an individual, series, or all slaves under a template
    For each slave generate the sql to apply to the slave DB using the DB name and table prefix stored in JMS
    Substitute keywords with data in configs etc
    Select to review the sql before applying to each slave or to just run them all
    Return status of executions

It would be the user's responsibility to backup the database before performing the update.

Thoughts??

As the utility matures could add the following capabilities:
    Emulate the update and show results
    Option to backup slave DB
    Do a snapshot of slave before and after for full analysis (testing only)
    Undo or restore capability
djdesjardins
Junior Boarder
Posts: 38
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#11496
Re:Maintence Tab Confusion 10 Years, 9 Months ago Karma: 54
Sorry but for the moment, I don't have more doc than the one that you have in the user manual.

Normally, the comparaison of the DB structure is possible with the maintenance menu.
It is possible to compare it either from
- "This site" because it is possible to read a remote slave site definition (see the settings menu)
- The master website that is the one found in the website definition and that can be different of the current (this site)
- From manifest or SQL files found on the disk. This case is better when there are also data included in the SQL scripts.
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 12
get the latest posts directly to your desktop
2Win, Multisite(s) are trademarks of Edwin2Win.
Joomla