Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-shell
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gitlab-shell
Commits
cd1faeef
Commit
cd1faeef
authored
May 05, 2016
by
Mark Campbell
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix spelling mistakes in README.md
parent
9bf99423
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
README.md
README.md
+2
-2
No files found.
README.md
View file @
cd1faeef
...
@@ -10,7 +10,7 @@ When you access the GitLab server over ssh then GitLab Shell will:
...
@@ -10,7 +10,7 @@ When you access the GitLab server over ssh then GitLab Shell will:
1.
Limits you to predefined git commands (git push, git pull, git annex).
1.
Limits you to predefined git commands (git push, git pull, git annex).
1.
Call the GitLab Rails API to check if you are authorized
1.
Call the GitLab Rails API to check if you are authorized
1.
It will execute the pre-receive hooks (called Git Hooks in GitLab Enterprise Edition)
1.
It will execute the pre-receive hooks (called Git Hooks in GitLab Enterprise Edition)
1.
It will excute the action you requested
1.
It will ex
e
cute the action you requested
1.
Process the GitLab post-receive actions
1.
Process the GitLab post-receive actions
1.
Process any custom post-receive actions
1.
Process any custom post-receive actions
...
@@ -34,7 +34,7 @@ The authorization checks for git pull are much simpler since you only have to ch
...
@@ -34,7 +34,7 @@ The authorization checks for git pull are much simpler since you only have to ch
An overview of the four cases described above:
An overview of the four cases described above:
1.
git pull over ssh -> gitlab-shell -> API call to gitlab-rails (Authorization) -> accept or decline -> execute git command
1.
git pull over ssh -> gitlab-shell -> API call to gitlab-rails (Authorization) -> accept or decline -> execute git command
1.
git pull over http -> gitlab-rails (A
U
thorization) -> accept or decline -> execute git command
1.
git pull over http -> gitlab-rails (A
u
thorization) -> accept or decline -> execute git command
1.
git push over ssh -> gitlab-shell (git command is not executed yet) -> execute git command -> gitlab-shell pre-receive hook -> API call to gitlab-rails (authorization) -> accept or decline push
1.
git push over ssh -> gitlab-shell (git command is not executed yet) -> execute git command -> gitlab-shell pre-receive hook -> API call to gitlab-rails (authorization) -> accept or decline push
1.
git push over http -> gitlab-rails (git command is not executed yet) -> execute git command -> gitlab-shell pre-receive hook -> API call to gitlab-rails (authorization) -> accept or decline push
1.
git push over http -> gitlab-rails (git command is not executed yet) -> execute git command -> gitlab-shell pre-receive hook -> API call to gitlab-rails (authorization) -> accept or decline push
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment