2019-09-04 21:01:54 +05:30
|
|
|
# Routing
|
|
|
|
|
|
|
|
|
|
The GitLab backend is written primarily with Rails so it uses [Rails
|
|
|
|
|
routing](https://guides.rubyonrails.org/routing.html). Beside Rails best
|
|
|
|
|
practices, there are few rules unique to the GitLab application. To
|
|
|
|
|
support subgroups, GitLab project and group routes use the wildcard
|
|
|
|
|
character to match project and group routes. For example, we might have
|
|
|
|
|
a path such as:
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
```
|
|
|
|
|
/gitlab-com/customer-success/north-america/west/customerA
|
|
|
|
|
```
|
2019-09-04 21:01:54 +05:30
|
|
|
|
|
|
|
|
However, paths can be ambiguous. Consider the following example:
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
```
|
|
|
|
|
/gitlab-com/edit
|
|
|
|
|
```
|
2019-09-04 21:01:54 +05:30
|
|
|
|
|
|
|
|
It's ambiguous whether there is a subgroup named `edit` or whether
|
|
|
|
|
this is a special endpoint to edit the `gitlab-com` group.
|
|
|
|
|
|
|
|
|
|
To eliminate the ambiguity and to make the backend easier to maintain,
|
|
|
|
|
we introduced the `/-/` scope. The purpose of it is to separate group or
|
|
|
|
|
project paths from the rest of the routes. Also it helps to reduce the
|
|
|
|
|
number of [reserved names](../user/reserved_names.md).
|
|
|
|
|
|
|
|
|
|
## Global routes
|
|
|
|
|
|
|
|
|
|
We have a number of global routes. For example:
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
```
|
|
|
|
|
/-/health
|
|
|
|
|
/-/metrics
|
|
|
|
|
```
|
2019-09-04 21:01:54 +05:30
|
|
|
|
|
|
|
|
## Group routes
|
|
|
|
|
|
|
|
|
|
Every group route must be under the `/-/` scope.
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
```
|
|
|
|
|
gitlab-org/-/edit
|
|
|
|
|
gitlab-org/-/activity
|
|
|
|
|
gitlab-org/-/security/dashboard
|
|
|
|
|
gitlab-org/serverless/-/activity
|
|
|
|
|
```
|
2019-09-04 21:01:54 +05:30
|
|
|
|
|
|
|
|
To achieve that, use the `scope '-'` method.
|
|
|
|
|
|
|
|
|
|
## Project routes
|
|
|
|
|
|
|
|
|
|
Every project route must be under the `/-/` scope, except cases where a Git
|
|
|
|
|
client or other software requires something different.
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
2019-09-30 21:07:59 +05:30
|
|
|
```
|
2019-12-21 20:55:43 +05:30
|
|
|
gitlab-org/gitlab/-/activity
|
|
|
|
|
gitlab-org/gitlab/-/jobs/123
|
|
|
|
|
gitlab-org/gitlab/-/settings/repository
|
2019-09-30 21:07:59 +05:30
|
|
|
gitlab-org/serverless/runtimes/-/settings/repository
|
|
|
|
|
```
|
2019-09-04 21:01:54 +05:30
|
|
|
|
|
|
|
|
Currently, only some project routes are placed under the `/-/` scope. However,
|
|
|
|
|
you can help us migrate more of them! To migrate project routes:
|
|
|
|
|
|
|
|
|
|
1. Modify existing routes by adding `-` scope.
|
|
|
|
|
1. Add redirects for legacy routes by using `Gitlab::Routing.redirect_legacy_paths`.
|
|
|
|
|
1. Create a technical debt issue to remove deprecated routes in later releases.
|
|
|
|
|
|
2019-12-04 20:38:33 +05:30
|
|
|
To get started, see an [example merge request](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/28435).
|
