Difference between revisions of "How to use sqlCVS from web admin"

From LinuxMCE
Jump to: navigation, search
m
 
m
Line 1: Line 1:
 +
[[Category:Tutorials| ]]
 +
 
In order to propagate your local changes to the community, the local changes from database need to be committed in central repository using [[sqlCVS]].
 
In order to propagate your local changes to the community, the local changes from database need to be committed in central repository using [[sqlCVS]].
  

Revision as of 14:44, 30 January 2008


In order to propagate your local changes to the community, the local changes from database need to be committed in central repository using sqlCVS.

Go to Advanced > sqlCVS > Diff

Default values for connection are:

 sqlCVS Host:  sqlcvs.linuxmce.org	
 Port: 	3999
 Username*: anonymous	
 Password*: anonymous	
 Database: pluto_main

Select the repositories and the tables you want to check for changes. If you don't know what tables were changed, you can select all of them, but be advised this will take a long time to complete.

If you only added a device template for example, you can select only dce repository, which will also select all tables in that repository. If you know what tables were changed, you can narrow the selection in order to run faster. After you made your selection, click "Next".

The page will call /usr/pluto/bin/sqlCVS with the parameters selected on page, who will run an integrity check first, then will display what changes are in selected repository and tables (new/changed/deleted records).

Each record added/changed/deleted will have a checkbox next to it, so you will be able to select what changes to checkin or revert. Once your selection is done, you can click at the very bottom of the page either on "Revert" or "Checkin" buttons.

 Important note: BEFORE you click "Revert" or "Checkin" you have to disable popup blocker for the current host.

Depending of the button you clicked, the operations you selected will be reverted or committed in sqlCVS main database. Be advised this may take a while, depending on the amount of records/tables used.