{"id":1066,"date":"2009-01-22T00:26:53","date_gmt":"2009-01-22T08:26:53","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=1066"},"modified":"2009-01-22T11:19:32","modified_gmt":"2009-01-22T19:19:32","slug":"version-control-for-system-administrators-part-1","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2009\/01\/22\/version-control-for-system-administrators-part-1\/","title":{"rendered":"Version control for System Administrators (Part 1)"},"content":{"rendered":"

1. Setting up ChangeVue 2009<\/strong><\/p>\n

Software developers have been using Source Code Control Systems for quite some years now. Most people involved with any kind of electronic files or document have a kind of ad-hoc version control usually using some file naming scheme.<\/p>\n

Something like:<\/p>\n

InfrastructureOct2007.doc
\nInfrastructureJan2008.doc
\nInfrastructureMar2008.doc<\/p>\n

Many administrators though, have stayed away from the developer oriented source control software packages. A feeling of overkill and the tendency to have a complicated setup can keep you away even if you recognize a basic need for that type of thing. After all, who wants to create databases on servers, user-ids, projects, and manage all that just to keep a few scripts under control.<\/p>\n

ChangeVue 2009 makes this a little simpler and scales more easily from a single user to a team system.<\/p>\n

The startup wizard makes short work of setting things up initially:<\/p>\n

\"image\"<\/a><\/p>\n

– You specify where to store your files’ versions: A “repository”, preferably somewhere on a NAS or some other network location.<\/p>\n

– You should provide a friendly name, which prevents you from having to deal with the full path name to your repository all the time.<\/p>\n

– The simplified user management just uses the name you specify rather than requiring you to login into yet another user-id\/password protected system.<\/p>\n

– It can automatically make ChangeVue the default source code control provider for PrimalScript.<\/p>\n

That’s pretty simple so far. Now all you have left is to set up a ‘project’ for your files. A ‘project’ is basically a folder in your repository. It’s just not called “folder” to avoid confusion when you talk about the two items in one sentence.<\/p>\n

\"image\"<\/a><\/p>\n

If you have all your scripts in one folder, you can simply map that one folder to a project. If you have a complete folder structure, just as easy, simply check the appropriate box.<\/p>\n

\"image\"<\/a><\/p>\n

Now all your files are under version control. It is worth to note at this time that all these files are now read-only on your local hard disk. This state is usually used by IDEs and text editors to determine that some file might be under version control.<\/p>\n

Note that even binary files, like ZIP files, bitmaps etc. can be part of a version control repository. ChangeVue’s binary difference mechanism will make certain that large files are not replicated over and over again.<\/p>\n

That’s it for part one. If you don’t need any other tool, you can even start editing your scripts right within ChangeVue.<\/p>\n

\"image\"<\/a><\/p>\n

I’ll be back with part two soon, showing you how to set up PrimalScript in one simple step to seamlessly work together with ChangeVue 2009.<\/p>\n","protected":false},"excerpt":{"rendered":"

1. Setting up ChangeVue 2009 Software developers have been using Source Code Control Systems for quite some years now. Most people involved with any kind of electronic files or document have a kind of ad-hoc version control usually using some file naming scheme. Something like: InfrastructureOct2007.doc InfrastructureJan2008.doc InfrastructureMar2008.doc Many administrators though, have stayed away from […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[440,283,311,21],"tags":[328,37,441,321],"class_list":["post-1066","post","type-post","status-publish","format-standard","hentry","category-changevue-software-news","category-howto","category-primaltools","category-software-news","tag-changevue","tag-primalscript","tag-source-code-control","tag-version-control"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/1066","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=1066"}],"version-history":[{"count":2,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/1066\/revisions"}],"predecessor-version":[{"id":1083,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/1066\/revisions\/1083"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=1066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=1066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=1066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}