moved services documentation

services/user-guide/gitlab/container.psi.ch.md

@@ -0,0 +1,9 @@
+# Container Registry
+
+__Under Construction!__
+
+The container registry is available under container.psi.ch. To push a container to the registry you need to tag it accordingly.
+
+``docker tag {MYCONTAINER} container.psi.ch/{NAMESPACE}/{YOURCONTAINER}:{TAG}``
+
+The container registry is only available inside the PSI-Network.

services/user-guide/gitlab/dependency_proxy.md

@@ -0,0 +1,26 @@
+# Dependency Proxy
+
+The dependency proxy in Gitlab is only able to pull images from docker hub. There is an epic on Gitlab.com to support other registries.
+https://gitlab.com/groups/gitlab-org/-/epics/6061
+ 
+## How to use the dependency proxy?
+
+Manually:
+ 
+Enable the dependency proxy in the desired group and use following command:
+``docker pull git.psi.ch/GROUPNAME/dependency_proxy/containers/IMAGENAME:TAG``
+ 
+``docker pull git.psi.ch/docker/dependency_proxy/containers/alpine:latest`` pulls the image to your computer “trough” the dependency proxy. If the image digest is the same on dockerhub and in the dependency proxy, it will pull from the proxy.
+ 
+ 
+Automated:
+
+``image: ${CI_DEPENDENCY_PROXY_DIRECT_GROUP_IMAGE_PREFIX}/alpine:latest``
+Add this to your .gitlab-ci.yml to use the proxy in your pipelines. You can find the exact line of code when you enable the dependency proxy in your group.
+ 
+https://docs.gitlab.com/ee/user/packages/dependency_proxy/#use-the-dependency-proxy-for-docker-images
+All the documentation can be found here.
+ 
+## Note
+
+The dependency proxy and the docker registry are not the same blob storage and therefore the images are also named differently. It is suggested to use the dependency proxy only in automated setups / pipelines.

services/user-guide/gitlab/git.psi.ch.md

@@ -0,0 +1,30 @@
+# General Information and Guideline
+
+__Under Construction!__
+
+To make a cut between internal development and external colaboration, there is two installations of Gitlab at PSI.
+For convenience reasons, we speak of Gitlab. If the information is specific to one instance it will be called by its URL. 
+
+## Comparison
+| Feature | gitlab.psi.ch | git.psi.ch |
+| :------ | ------- | ---------------: |
+| Container Registry | No | Yes |
+| RPM Registry | Yes | Yes |
+| Gitpages | No | Yes |
+| ACL for Gitpages | No | Yes |
+| LFS | Yes | Yes |
+| Public accessible | Yes | No |
+
+## User Management
+Every PSI User is allowed to login to Gitlab, to work with non PSI Users, these must first be registered in AD. This can be done in [SNOW](https://intranet.psi.ch/en/computing/request-accounts-for-external-collaborators) (Beware Page is a little out of date)
+The user must have logged in first to Gitlab that it can be added to any group or project.
+Make sure to upload an SSH public key to your Gitlab profile to be able to push and pull code with SSH.
+
+Sign-up and local Users are disabled.
+
+## Runners
+There are 2 shared Gitlab runners to use, if you want to use deticated runners, these must be registered first and the option to use shared runners disabled in the project options.
+Runners are in the responsability of the owner, if there are any changes, we will inform the users accordingly.
+
+## Availability
+There is no SLA on Gitlab, but we do our best to have it available like other linux services     during office hours. 

services/user-guide/gitlab/gitlab.md

@@ -0,0 +1,8 @@
+# Gitlab
+
+__Still under construction !!!__
+
+Documentations that can be found here:
+- (Gitlab) git.psi.ch
+- (Container Registry) container.psi.ch
+- (Git Pages) gitpages.psi.ch

services/user-guide/gitlab/gitlab_cli.md

@@ -0,0 +1,34 @@
+# Gitlab CLI
+
+To interact with your gitlab instances via CLI you can use the Gitlab CLI tool: https://gitlab.com/gitlab-org/cli
+
+
+## Installation
+
+On a standard PSI RHELX system you can install the CLI client via:
+```
+yum install glac
+```
+
+Otherwise please head over to https://gitlab.com/gitlab-org/cli/-/releases and download/install the client for your platform.
+
+## Usage
+
+Configuration for your instance:
+```
+glab config set -g host git.psi.ch
+```
+
+Global configuration file can be found:
+`~/.config/glab-cli/config.yml`
+
+Authentication 
+- Create access token with at least **API** and **write_repository** permissions: https://git.psi.ch/-/profile/personal_access_tokens?scopes=api,write_repository
+
+```
+glab auth login --hostname git.psi.ch --token <yourtoken>
+```
+
+After authentication you can work with the `glab` command as documented on:
+https://gitlab.com/gitlab-org/cli#core-commands
+

services/user-guide/gitlab/gitpages.psi.ch.md

@@ -0,0 +1,8 @@
+# Pages
+__Under Construction!__
+
+Gitpages can be used to display static HTTP content. Per default, gitpages are readable by everyone. You can change this behaviour in your project settings in the general tab under "visibility, project features, permissions" to only allow authenticated users to read your page.
+ 
+To make gitpages accessible with a different (more speaking name) one can order a DNS entry in ServiceNow like linux.psi.ch :)
+
+Gitpages are only available inside the PSI Network and only on git.psi.ch (internal gitlab)