forked from pivotal-cf/docs-gitlab
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ssh.html.md.erb
32 lines (18 loc) · 1.37 KB
/
ssh.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
---
title: GitLab
owner: Partners
---
The GitLab Enterprise tile supports SSH access directly to GitLab nodes. All nodes share an SSH host-key that is generated securely by the tile.
GitLab users will need to add an SSH key to their account by following the guide on [gitlab.com](http://doc.gitlab.com/ee/ssh/README.html) before they can access git functionality via SSH.
## Direct access
Identity a GitLab node IP address via the resources tab in the GitLab tile.
If you have a firewall in place you will need to add an exception for the external IP address(s) that will be accessing the GitLab node via SSH. GitLab nodes listen on port 2222 for inbound git SSH traffic.
### Example usage
`git clone ssh://git@gitlab-node-ip:2222/user/repo.git`
## Access via Load Balancer
If you want to provide a more standard git experience you can manually set up and configure an external load balancer to point to a given GitLab node. This should route traffic from port 22 to port 2222 on the GitLab node. You can then point a DNS record at the load balancer.
### Example usage
`git clone [email protected]:user/repo.git`
# Roadmap
In the future we plan to use the Cloud Foundry TCP router (currently under development) to a provide a URL for SSH access. The `git remote` details on any cloned repo's will need to be updated.