Google tag

Pages

How can I import my existing repository into newly installed VisualSVN Server?




Importing incompatible or remote repository

If your existing repository has incompatible format, it should be converted to the supported one. If your existing repository is located on another server, it should be moved to the computer where VisualSVN Server is installed. Both tasks can be performed by exporting ("dumping") the repository contents to a file of a special format ("dump file") on its native SVN server and then loading this dump into newly set up VisualSVN Server with the help of svnadmin utility. Svnadmin is the administrative tool for monitoring and repairing your Subversion repository and is distributed as a part of VisualSVN Server installation.

To import incompatible or remote repository, perform the following steps:
Create dump of a repository using your existing Subversion version
Copy dump file to the local computer, if required
Import dump into newly installed VisualSVN Server


Creating repository dump using existing Subversion version

To dump the contents of the repository, perform the following steps on the server where your existing repository is located:
Start command prompt interpreter.
Perform the following command:
PATH-TO-SVN\svnadmin dump PATH-TO-REPO > PATH-TO-DUMPwhere
PATH-TO-SVN - path to your old Subversion installation;
PATH-TO-REPO - path to the repository folder;
PATH-TO-DUMP - full path to the dump file.

For example:
c:\Program Files\Subversion\bin\svnadmin dump c:\repositories\Contoso > c:\repo.dump



Depending on the repository size, this operation can take considerable time. You can watch the status output of the operation in your terminal window.

ImportantRepository dump should be created using the svnadmin utility from the corresponding Subversion installation used to create this repository.


Copying repository dump to the local computer

If your existing repository is located on another server, copy the dump file to the computer with your newly installed VisualSVN Server. Dump file is written in a portable format, so it can be copied between different software platforms (for example, from Linux to Windows)
Importing repository dump into newly installed VisualSVN Server

To import a repository dump, perform the following steps in your new VisualSVN Server:
Create new empty repository. To do that:
Open VisualSVN Server Manager by selecting Start | All Programs | VisualSVN and clicking VisualSVN Server Manager;
Right-click the Repositories node and select Create New Repository;
Specify the name for the new repository;
Do not select the Create default structure (trunk, branches, tags) check box as repository should be empty;
Click OK.
Load a repository dump stream from the created dump file performing the following command:

"%VISUALSVN_SERVER%\bin\svnadmin" load PATH-TO-NEW-REPO < PATH-TO-DUMP
where
PATH-TO-NEW-REPO - path to the created repository folder;
PATH-TO-DUMP - full path to the dump file.

Notes
To be sure that the correct Subversion version (the one provided with VisualSVN Server) is used to load the dump, use the %VISUALSVN_SERVER% environment variable to locate the svnadmin executable file. Alternatively, to locate the correct version of svnadmin executable, you can use the Start a new instance of command interpreter command on the VisualSVN Server Manager toolbar to launch the terminal window.
The Subversion repository dump format describes versioned repository changes only. It will not carry any information about uncommitted transactions, user locks on file system paths, repository or server configuration customizations (including hook scripts), and so on.

After performing this command, all the data from the existing repository will be moved to the new one and the new repository will be available for use with VisualSVN Server.






http://www.visualsvn.com/support/topic/00010/

Use JqueryMobile in PhoneGap Must Do!


So in PhoneGap apps that must "phone home" by loading assets off a remote server, both the $.support.cors AND $.mobile.allowCrossDomainPages must be set to true. The $.mobile.allowCrossDomainPages option must be set before any cross-domain request is made so we recommend wrapping this in a mobileinit handler:      

       
        <script>
$( document ).bind( "mobileinit", function() {
// Make your jQuery Mobile framework configuration changes here!
$.support.cors = true;
$.mobile.allowCrossDomainPages = true;
});
        </script>