actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update valet-configure-lab.md

Browse Source
This commit is contained in:
j-dunham
2022-08-10 09:22:39 -04:00
committed by GitHub
parent 63c17d26ed
commit 274d07e968
1 changed files with 16 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gitlab/valet-configure-lab.md
+16 -8
View File
@@ -1,4 +1,4 @@
# Configure GitLab using Valet `configure` command # Configure Valet To Work With GitLab Using The `configure` Command
In this lab, you will use Valet's `configure` command to set up the required secrets to communicate with the GitLab and GitHub instances. The `configure` command can be used for all of the supported providers, but in this lab we will be focusing on GitLab. In this lab, you will use Valet's `configure` command to set up the required secrets to communicate with the GitLab and GitHub instances. The `configure` command can be used for all of the supported providers, but in this lab we will be focusing on GitLab.
- [Prerequisites](#prerequisites) - [Prerequisites](#prerequisites)
@@ -18,13 +18,21 @@ In this lab, you will use Valet's `configure` command to set up the required sec
3. Hover over the address under the `Local Address` column, and click the globe to open in browser 3. Hover over the address under the `Local Address` column, and click the globe to open in browser
4. Login to the GitLab server and following [instructions](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) to generate a token that has `read_api` scope. 4. Login to the GitLab server and following [instructions](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token) to generate a token that has `read_api` scope.
5. Record token for use in later steps. 5. Record token for use in later steps.
3. In the codespace terminal run `gh valet configure`. 3. Create a GitHub personal access token.
4. Using the down arrow key to highlight `GitLab CI`, press the spacebar to select, then hit enter to accept. - Navigate to your GitHub `Settings` - click your profile photo and then click `Settings`.
5. Enter the previously generated GitHub access token. - Go to `Developer Settings`
6. Enter the GitHub instance url or hit enter to accept the default, if you are using github.com - Go to `Personal Access Tokens` -> `Legacy tokens (if present)`
7. Enter the GitLab access token from step 2 and press enter. - Click `Generate new token` -> `Legacy tokens (if present)`. If required, provide your password.
8. Enter `http://localhost` for the GitLab instance url - Select at least these scopes: `read packages` and `workflow`. Optionally, provide a text in the **Note** field and change the expiration.
9. If all went well you should see a similar output in your terminal - Click `Generate token`
- Copy the token somewhere safe and temporary.
4. In the codespace terminal run `gh valet configure`.
5. Using the down arrow key to highlight `GitLab CI`, press the spacebar to select, then hit enter to accept.
6. Enter the previously generated GitHub access token from step 3.
7. Enter the GitHub instance url or hit enter to accept the default, if you are using github.com
8. Enter the GitLab access token from step 2 and press enter.
9. Enter `http://localhost` for the GitLab instance url
10. If all went well you should see a similar output in your terminal
ADD_IMAGE_HERE ADD_IMAGE_HERE
## Verify Valet Works ## Verify Valet Works