-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add git lab and slightly change comment
- Loading branch information
1 parent
b173de8
commit a817121
Showing
3 changed files
with
91 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,89 @@ | ||
--- | ||
title: 1.1 Git Repository | ||
weight: 11 | ||
sectionnumber: 1.1 | ||
--- | ||
|
||
In this lab, we set up our own git repository with [Gitea](https://about.gitea.com/) for later use. Basic knowledge of [git](https://git-scm.com) is supposed. If you are not familiar with git, you can learn everything about it here: [https://git-scm.com/book/en/v2](https://git-scm.com/book/en/v2) | ||
|
||
There is also extensive documentation of Gitea available at [https://docs.gitea.com/](https://docs.gitea.com/). | ||
|
||
### Task 1 | ||
|
||
Login to gitea at `https://<yourname>-controller.workshop.puzzle.ch:4000` and create your own repository `techlab`. | ||
|
||
{{% details title="Solution Task 1" %}} | ||
|
||
* Navigate your webbrowser to `https://<yourname>-controller.workshop.puzzle.ch:4000` . Be sure to use port 4000. | ||
* In the upper right corner click on `Sign In`. | ||
* Enter your username and password provided by the teacher. Then click the green button `Sign In`. | ||
* Klick on the `+` sign to the right of `Repostories`. | ||
* Enter `techlab` as repository name and click `create repository`. | ||
|
||
{{% /details %}} | ||
|
||
### Task 2 | ||
|
||
Now we initialize the `/home/ansible/techlab` folder as a local git repository and add the gitea repository created in Task 1 as its remote. We also do some basic git configurations. | ||
|
||
* On the controller server go to the techlab folder | ||
* Config `main` as the default branch | ||
* Config your name and email | ||
* Init a git repo in the `/home/ansible/techlab` folder | ||
* Add your gitea repository as an ssh-remote ( the remote ssh user is gitea, so `gitea@<yourname>-controller.workshop.puzzle.ch:ansible/techlab.git` is what you have to set as a remote). | ||
* Create a `README.md` file with a description of your repository | ||
* Add and commit the file `README.md` with an appropriate commit message. | ||
* Don't push your changes yet | ||
* Push your changes to the remote repository on gitea | ||
|
||
{{% details title="Solution Task 2" %}} | ||
|
||
``` | ||
cd /home/ansible/techlab | ||
git config --global init.defaultBranch main | ||
git config --global user.email "[email protected]" | ||
git config --global user.name "Your Name" | ||
git init | ||
git remote add origin gitea@<yourname>-controller.workshop.puzzle.ch:ansible/techlab.git | ||
echo "This is my Ansible Techlab repo" > README.md | ||
git add README.md | ||
git commit -m "first commit" | ||
git push --set-upstream origin main | ||
``` | ||
|
||
{{% /details %}} | ||
|
||
### Task 3 | ||
|
||
* In Task 2 of Lab 1.0 you created ssh keys for the user ansible | ||
* Show the content of the ssh public key | ||
* In the Gitea GUI, navigate to the `Settin`s` of your user | ||
* Then go to the `SSH / GPG Keys` tab of the `Settings` | ||
* Click the `Add Key` button | ||
* Set `ansible@<yourname>-controller` as `Key Name` and paste the content of your public key in the `Content` field of the GUI | ||
* Click `Add Key` | ||
|
||
{{% details title="Solution Task 3" %}} | ||
|
||
``` | ||
cat /home/ansible/.ssh/id_rsa.pub | ||
``` | ||
|
||
![Add ssh keys](git_add_sshkey_to_gitea.png) | ||
|
||
{{% /details %}} | ||
|
||
### Task 4 | ||
|
||
* Push your changes and set the upstream to `origin main` | ||
* In the Gitea GUI, check, that your changes have been pushed to the remote. | ||
|
||
{{% details title="Solution Task 4" %}} | ||
|
||
``` | ||
git push --set-upstream origin main | ||
``` | ||
|
||
(If you push for the first time, check and then accept the controllers authenticity by entering `yes` followed by `<ENTER>`) | ||
|
||
{{% /details %}} |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
--- | ||
title: 9. AWX | ||
weight: 90 | ||
sectionnumber: 9.2 | ||
sectionnumber: 9.0 | ||
--- | ||
|
||
[AWX](https://github.com/ansible/awx) provides a web-based user interface, REST API, and task engine built on top of Ansible. CIQ's [Ascender](https://ciq.com/products/ascender/) and Red Hat's [AAP](https://www.redhat.com/en/technologies/management/ansible) are based on AWX. | ||
|
||
Since the installation of Ascender is the most convenient, we use Ascender as the tool to learn about AWX Automation Platform. | ||
Since the installation of Ascender is the most convenient, we use Ascender. |