Changes between Version 1 and Version 2 of TracUserSyncPlugin


Ignore:
Timestamp:
Oct 31, 2009 8:48:48 PM (5 years ago)
Author:
izzy
Comment:

Description updated

Legend:

Unmodified
Added
Removed
Modified
  • TracUserSyncPlugin

    v1 v2  
    11= Synchronize User Account data between multiple Trac projects = 
    2  
    3 == Description == 
    4  
    5 To be used to synchronize user account data between multiple projects within the same TRAC_PARENT 
    62 
    73{{{ 
    84#!html 
    9 <DIV STYLE="background: #fdc; border: 2px solid #d00; color: #500; padding: .5em; margin: 1em 0;"> 
    10 <B STYLE="color:#f00">WARNING:</B> This plugin is at best an early beta. So take special care using it, especially in productive environments! 
    11 </DIV> 
     5<DIV STYLE='background: #fdc; border: 2px solid #d00; color: #500; padding: .5em; margin: 1em 0;'> 
     6<B STYLE='color:#f00;'>WARNING:</B> This plugin is at best an early beta. So take special care using it, especially in productive environments! 
     7</DIV> 
    128}}} 
    139 
     10== Description == 
     11This plugin can be used to synchronize user account data between multiple projects within the same `TRAC_PARENT`. Basically, it reads the account information from all the separate environments, merges them, and then updates all environments accordingly. As it currently still is in early beta state at best, a `dryrun` mode is enabled by default - so no changes will be written to the database. Instead, the updates for the affected environments will be stored in `<tracenv>.sql` files to investigate. 
     12 
     13If you intend to use this plugin in its current state, you are strongly encouraged to... 
     14 1. first test it in a non-productive environment, which best is a copy of the intended productive environment to be used on later 
     15 1. first let it run in `drymode`, and investigate the resulting `*.sql` files carefully 
     16 1. only if everything seems to be fine, and still being in your test environment, and after making a copy of the databases, disable `drymode` and verify the results 
     17 1. only if still everything seems to be OK, repeat these steps in your productive environment - at your own risk 
     18 
     19I (the author) will take no responsibilities whatever, especially concerning possible damage and data loss. You have been warned! 
     20 
     21If you are still encouraged to try it: Great - I love to receive your feedback! 
     22 
     23== Limitations == 
     24Except this plugin being still in early beta state, there are more limitations to consider: 
     25 1. it was not widely tested yet 
     26 1. it is not yet "fool-proof" (if it ever will be). This especially means, not all possible exceptions may be handled yet 
     27 1. it works only for environments, which... 
     28  1. share the same `TRAC_PARENT_DIR` 
     29  1. use the AccountManagerPlugin 
     30  1. store the user passwords in a `.htpasswd` file 
     31  1. share the same `.htpasswd` password file (which at the moment '''''you''''' have to ensure, it's not yet verified) 
     32There may be more limitations I'm not aware of at the moment... 
    1433 
    1534== Bugs/Feature Requests ==