|
|
|
# 1 First steps
|
|
|
|
Go to https://webis16.medien.uni-weimar.de/gitlab and log in with your university account if you haven't done so already. This is the same username and password that you have been using for our CVS. On your first login, your gitlab account will be created automatically.
|
|
|
|
Go to the [GitLab Main Page](https://webis16.medien.uni-weimar.de/gitlab) and log in with your university account if you haven't done so already. This is the same username and password that you have been using for our CVS. On your first login, your GitLab account will be created automatically.
|
|
|
|
|
|
|
|
You may not be able to see any projects yet, because you need to be granted access by one of our staff; if you have registered your account some time ago and still can't access any projects, please notify the `webisstud` mailing list.
|
|
|
|
|
|
|
|
|
|
|
|
# 2 Exploring GitLab
|
|
|
|
Once you have access, you will see our projects at https://webis16.medien.uni-weimar.de/gitlab/explore/projects/
|
|
|
|
Once you have access, you will see our projects in the [Explore Projects Tab](https://webis16.medien.uni-weimar.de/gitlab/explore/projects/)
|
|
|
|
|
|
|
|
The projects are organized in mostly the same way that they were in CVS. Top-level folders under `code-in-progress` are now called *groups* in GitLab. For instance `webisstud` is now a group with the URL https://webis16.medien.uni-weimar.de/gitlab/webisstud.
|
|
|
|
|
|
|
|
You can see a list of all groups here https://webis16.medien.uni-weimar.de/gitlab/explore/groups
|
|
|
|
You can see a list of all groups in the [Explore Groups Tab](https://webis16.medien.uni-weimar.de/gitlab/explore/groups)
|
|
|
|
|
|
|
|
Each former CVS module on the second level of the hierarchy is now a *project* in GitLab, and has its own Git repository. For example, the project `code-in-progress/webisstud/wstud-clickbait-ws16` is now project `wstud-clickbait-ws16` in group `webisstud` with the URL https://webis16.medien.uni-weimar.de/gitlab/webisstud/wstud-clickbait-ws16
|
|
|
|
Students will by default get full write access to the two groups `webisstud` and `thirdparty`. Projects within these groups will also be listed under [My Projects](https://webis16.medien.uni-weimar.de/gitlab/dashboard/projects). If you need access to other groups or repositories, please ask our staff.
|
|
|
|
|
|
|
|
Each former CVS module on the second level of the hierarchy is now a *project* in GitLab, and has its own Git repository. For example, the project `code-in-progress/webisstud/wstud-clickbait-ws16` is now a project `wstud-clickbait-ws16` in group `webisstud` with the URL https://webis16.medien.uni-weimar.de/gitlab/webisstud/wstud-clickbait-ws16
|
|
|
|
|
|
|
|
|
|
|
|
# 3 Authentication, Cloning and Updating Projects
|
| ... | ... | @@ -23,7 +25,7 @@ ssh-keygen -t rsa -b 4096 |
|
|
|
|
|
|
|
and following the instructions. Although not required, it is recommended to set a password for encrypting your private key.
|
|
|
|
|
|
|
|
Once your SSH key has been generated, copy the contents of `~/.ssh/id_rsa.pub` (or whatever file you chose to store your public key in) into the *Key* field at https://webis16.medien.uni-weimar.de/gitlab/profile/keys and click *Add Key*. This will add the public key to your GitLab account, so you can use you the corresponding private key to pull from and push to GitLab via SSH. Make sure to keep the private key part in `~/.ssh/id_rsa` secret at all times! If your private key gets compromised, delete the public key from GItLab and create a new key pair to prevent others from gaining unauthorized access to our Git repositories.
|
|
|
|
Once your SSH key has been generated, copy the contents of `~/.ssh/id_rsa.pub` (or whatever file you chose to store your public key in) into the *Key* field in your [SSH Key Settings](https://webis16.medien.uni-weimar.de/gitlab/profile/keys) and click *Add Key*. This will add the public key to your GitLab account, so you can use you the corresponding private key to pull from and push to GitLab via SSH. Make sure to keep the private key part in `~/.ssh/id_rsa` secret at all times! If your private key gets compromised, delete the public key from GItLab and create a new key pair to prevent others from gaining unauthorized access to our Git repositories.
|
|
|
|
|
|
|
|
If you are using the `webis` command (see next section), then `webis git init` will automatically create an SSH key pair for you if you don't have one.
|
|
|
|
|
| ... | ... | @@ -100,6 +102,6 @@ If you use IntelliJ IDEA, there is a slightly more convenient process with the * |
|
|
|
|
|
|
|
From there, go to *Settings* to configure the plugin, enter https://webis16.medien.uni-weimar.de/gitlab as URL.
|
|
|
|
|
|
|
|
The *Access Token* must be generated from your GitLab profile page at https://webis16.medien.uni-weimar.de/gitlab/profile/personal_access_tokens.
|
|
|
|
The *Access Token* must be generated from your [GitLab Profile Page](https://webis16.medien.uni-weimar.de/gitlab/profile/personal_access_tokens).
|
|
|
|
|
|
|
|
After you click *Refresh*, you will see our project groups, which you can expand to find and clone individual projects. |
|
|
\ No newline at end of file |
