Changes between Version 5 and Version 6 of GitVersionControl
- Timestamp:
- 11/07/17 17:05:07 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GitVersionControl
v5 v6 2 2 3 3 == Overview == 4 === Shared Access to Identity and Access Management Repositories === 4 5 Identity and Access Management has access to three contexts in University of Alaska GitHub Repository: 5 6 * Personal (identified by UA Username) … … 9 10 Within the OIT - IAM repository, there are two types of repositories, those that represent a Chef managed system and those that contain Source files. 10 11 12 === Individual Repositories === 13 In addition to OIT - IAM repositories, each user can develop and share private repositories. 14 11 15 == Choosing a Context == 16 17 === Choosing a shared OIT - IAM Context === 12 18 Once logged in by default, the context will be set to a user's personal repository. A drop down button allows the user to select the desired context for IAM activities. 13 19 14 20 [[Image(AK github context selection.png)]][[br]] 15 21 16 === Identifying Chef Cookbooks versus Source Files ===22 === Identifying OIT - IAM Chef Cookbooks versus Source Files === 17 23 A convention has been established for identifying which repositories contain Chef cookbooks, i.e., the configuration for an entire system, or source files to run an application. By convention, anything that is a cookbook follows the naming format of OIT-IAM/iam-<application name>-app. 18 24 … … 21 27 [[Image(AK OIT IAM repositories.png)]][[br]] 22 28 23 === Contents of Chef Cookbook Repository ===29 === Contents of an OIT - IAM Chef Cookbook Repository === 24 30 Below is an example of a Chef Cookbook repository. Notice a few of the keywords used to indicate standard Chef directories and files such as, recipes, kitchen.yml, metadata.rb 25 31 26 32 [[Image(OIT IAM example github cookbook.png)]][[br]] 27 33 28 === Contents of a Source File Repository ===34 === Contents of an OIT - IAM Source File Repository === 29 35 The source files for people, as opposed to the Chef Cookbook, contain no set pattern, other than what is needed for the application itself. 30 36 … … 32 38 33 39 == Pulling a Repository to a Local Desktop == 34 Login into github.alaska.edu 35 Use UA Username and password to login 36 Check repositories for latest work 40 The following steps are describing how to clone an individual user's repository. 41 42 * Login into github.alaska.edu 43 * Use UA Username and password to login 44 * Check repositories for latest work 37 45 Image of curent repositories 38 Click on desired repository to get address to clone it39 Click on clone or download down arrow (copy or copy to clipboard) will copy the repository location.40 Go to terminal window41 Either create directory for location or if in a desired hierarchytype46 * Click on desired repository to get address to clone it 47 * Click on clone or download down arrow (copy or copy to clipboard) will copy the repository location. 48 * Go to terminal window 49 * Either create directory for location or if in a desired hierarchy, then type 42 50 {{{ 43 51 git clone git@github.alaska.edu:serie/SelfServiceAttributes.git 44 52 }}} 45 53 46 Remember to pull before any edit and push often54 * Remember to pull before any edit and push often 47 55 48 56 49 57 50