![]() Navigate to the folder on the production environment > Right click in the whitespace > SVN Checkout.After completing development and testing the code, you'll be ready to deploy it to a production environment.A dialog will display stating that the directory selected is not empty > Confirm the target folder path and Click CheckoutÄeploying Updates with Subversion Workflow.Verify the checkout path, making sure no unwanted sub-directories were added based on the repository URL (for example, I've found that TortoiseSVN will add /trunk to the checkout directory). ![]() Input the URL to the repository to work with.To convert the current directory into a working directory after successfully importing the code into the repository, simply right click in the whitespace > SVN Checkout.Input a meaningful comment about the state of the code being imported.Right click in the whitespace > TortoiseSVN > Import.Navigate to the folder that contains your code.Create the Subversion repository using the steps above.Input meaningful comments about the changes completed.After completing code changes, right click in the white space of the working directory > SVN Commit.Input the URL to the repository to work with, this can be either a file:// or http(s):// URL if Apache HTTPD has been setup for Subversion (Video link: ).Inside the new application folder, right click in the whitespace > SVN Checkout.Create a folder to contain the working copy of the code, this could be on a development web server.When the dialog appears, click the Create folder structure option, this will create the standard "trunk", "branches" and "tags" directories inside the new repository. ![]() ![]()
0 Comments
Leave a Reply. |