UMIACS - User contributions [en]

GitLab

2019-03-25T18:15:13Z

Chrissul: Updating Authentication Info

GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.

All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.

To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:

https://gitlab.umiacs.umd.edu

Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client.
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.

==GitLab Offsite Collaborators==
Any UMIACS user can now create an unlimited number of offsite
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create
repositories or groups, but may be given access to your repositories or
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].

==User Documentation==
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.

Some of the most useful sections include:
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md

==Repository URLs==
Users can download and clone directories from the remote repository using git clone. There are two different URLs that can be used: HTTPS and SSH.
You can view the URL underneath the Project title in the Project tab. Change the displayed URL by clicking on the URL type you want to see.
===SSH===
The SSH URL is more direct, though it is harder to set up. In order to do so, you will have to add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can log in without having to enter any credentials from the machine and account for which you created the SSH key.
===HTTPS===
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.

==Make GitLab projects public==
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public and make repo accessible to everyone, follow the steps below:
1. Go to your projects page https://gitlab.umiacs.umd.edu/<username>/<yourProjectName>.
For example: https://gitlab.umiacs.umd.edu/suzantrt/someNewAwesomeProject
2. Click on '''Settings'''.

3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.

4. Scroll down and click on '''Save Changes'''

5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.

6. Click on '''Save Changes'''.

Now your project has become public with its repository accessible anyone with access.

SecGroups

2018-08-07T18:05:00Z

Chrissul: Formatting

Security Groups are authentication groups that control access to various applications in UMIACS. They provide fine-grained access control to wikis, source code repositories, and certain web applications.

==Viewing/Editing Security Groups==

You can view and edit the secgroups you belong to using the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]

SecGroups

2018-08-07T18:04:42Z

Chrissul: Creating Page

==Security Groups==

Security Groups are authentication groups that control access to various applications in UMIACS. They provide fine-grained access control to wikis, source code repositories, and certain web applications.

==Viewing/Editing Security Groups==

You can view and edit the secgroups you belong to using the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]

PrinterQueueNaming

2018-04-05T15:26:11Z

Chrissul: Updated graphic

==Printer Queues==

UMIACS uses a centralized print server to manage all of the printers in the Institute. See [Printing] for more details specific to your OS. We have developed a naming scheme for our printer queues based on the colors the printer can produce, the type of queue, and the room number.

The naming scheme is as follows:

* All color printers begin with a "c". Black & white is the default so nothing extra is needed.
* Then is either "ps" for a postscript queue or "pcl" for a PCL queue. Postscript and PCL are types of printer drivers. If you are unsure what this means, use "ps" for postscript.
* Then add the room number. All printers in the Bio Sciences Building also add the building number. E.g., room 3120H in BSB is "296-3120H" while room 3142 in AV Williams is "3142".

[[Image:PrinterNamingUpdated.png]]

Some examples:

* cps3142 is a color printer in AV Williams 3142.
* ps3142 is a black & white printer in AV Williams 3142.
* pcl3142 is a black & white printer in AV Williams 3142 but uses a PCL driver.
* cps296-3120H is a color printer in BSB.

PrinterQueueNaming

2018-04-05T15:21:20Z

Chrissul:

==Printer Queues==

UMIACS uses a centralized print server to manage all of the printers in the Institute. See [Printing] for more details specific to your OS. We have developed a naming scheme for our printer queues based on the colors the printer can produce, the type of queue, and the room number.

The naming scheme is as follows:

* All color printers begin with a "c". Black & white is the default so nothing extra is needed.
* Then is either "ps" for a postscript queue or "pcl" for a PCL queue. Postscript and PCL are types of printer drivers. If you are unsure what this means, use "ps" for postscript.
* Then add the room number. All printers in the Bio Sciences Building also add the building number. E.g., room 3120H in BSB is "296-3120H" while room 3142 in AV Williams is "3142".

[[Image:Printernaming.jpg]]

Some examples:

* cps3142 is a color printer in AV Williams 3142.
* ps3142 is a black & white printer in AV Williams 3142.
* pcl3142 is a black & white printer in AV Williams 3142 but uses a PCL driver.
* cps296-3120H is a color printer in BSB.