Move any Kando 2012.1 repositories from their old storage area to the new GitCentric storage area at <destination_path> (typically <gc_home>/site/git ) after an upgrade installation. mvrepos identifies the old storage area by querying the database.
mvrepos checks that the target path exists and is writable. It only looks at acrepository records that are not hidden (deleted). If there is a null or empty path in any of the acrepository records, no moves will be attempted. Any of the above conditions will return error messages as well as a return status of 1. During the individual moves and database updates, if a single move fails, the others will still be attempted. There will be error messages for each move that fails and the overall return status will be 1. Therefore, you can re-run this command after fixing a failure condition, so that eventually all repos are moved. If all moves are successful, no message is displayed and a 0 is returned for status.
kandoMaintain mvrepos -u <dbadmin> -P <dbpass> -r <repository_path>
jdbc:postgresql://<host>:<port>/<dbname>If you do not specify -c for a command that requires it, kandoMaintain assumes the default value jdbc:postgresql://localhost:5075/kando. If you do specify -c, then jdbc:postgresql:// at a minimum is required. Partial connection strings will have default values automatically supplied. For example, if you specify jdbc:postgresql://, kandoMaintain assumes a <host> of localhost, a <port> value of 5075 and a <dbname> of kando.
For example:
DB_USER=postgres DB_PASS=postgres DB_CONNECT =dbc:postgresql://localhost:5075/kando