You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/book/04-git-server/chapter4.asc
+22-7Lines changed: 22 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -679,18 +679,35 @@ These range from ``Guest'' (issues and chat only) to ``Owner'' (full control of
679
679
The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen.
680
680
681
681
===== Projects
682
-
* Visibility levels
683
-
* Labels
682
+
683
+
A GitLab project roughly corresponds to a single git repository.
684
+
Every project belongs to a single namespace, either a user or a group.
685
+
If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group's user-level permissions will also take effect.
686
+
687
+
Every project has a visibility level, which controls who has read access to that project's pages and repository.
688
+
If a project is _Private_, the project's owner must explicitly grant access to specific users.
689
+
An _Internal_ project is visible to any logged-in user, and a _Public_ project is visible to anyone.
690
+
Note that this controls both git "fetch" access as well as access to the web UI for that project.
691
+
692
+
Projects can also have labels, which can help organize projects across namespaces.
693
+
The projects dashboard page can filter the displayed repositories by one or more labels.
694
+
This is helpful if you have a large number of projects in different groups, but that relate in some way.
684
695
685
696
===== Other Tools
686
-
* Hooks
687
-
* Logs
688
-
* Messages
697
+
698
+
GitLab includes support for *Hooks*, both at a project or system level.
699
+
For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur.
700
+
This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools.
701
+
702
+
The *Message* feature is useful to broadcast information about the system to all users.
703
+
A maximum of one message is visible at any given time, and every message has a window of time during which it is visible to any user (including anonymous ones).
689
704
690
705
[[gitlab_message]]
691
706
.How a message is displayed.
692
707
image::images/gitlab-broadcast.png[How a message is displayed.]
693
708
709
+
This is typically used for system status information (_"The server will be undergoing maintenance…"_), but administrative users have full control over the content and color scheme.
710
+
694
711
==== Basic Operation
695
712
696
713
* Creating a project
@@ -705,8 +722,6 @@ image::images/gitlab-broadcast.png[How a message is displayed.]
0 commit comments