| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| |
| |
| |
| | |
work [ci skip]
|
| | |
|
| |
| |
| |
| |
| |
| | |
shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future"
This reverts commit 86a2a78f0d13a678899460638add6b862059433e.
|
| |
| |
| |
| | |
shared/pages/fqdn/subpath/public - makes it simpler to implement CNAMEs in future
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The pages are created when build artifacts for `pages` job are uploaded
- Pages serve the content under: http://group.pages.domain.com/project
- Pages can be used to serve the group page, special project named as host: group.pages.domain.com
- User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
- Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
- The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
- The public/ is extracted from artifacts and content is served as static pages
- Pages asynchronous worker use `dd` to limit the unpacked tar size
- Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
- Pages are part of backups
- Pages notify the deployment status using Commit Status API
- Pages use a new sidekiq queue: pages
- Pages use a separate nginx config which needs to be explicitly added
|
| |
|
| |
|
|\
| |
| | |
Fix gitlab-ssl nginx config to work when multiple server_names are served over https
|
| |
| |
| |
| | |
over https
|
|/
|
|
|
|
| |
are up and running
Closes https://github.com/gitlabhq/gitlabhq/issues/9869
|
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
| |
It turns out that if we do not the declaration from
"location /" wins.
|
|\
| |
| |
| |
| |
| |
| | |
Do not limit workhorse POST/PUT size in NGINX
Limiting, if any, should happen in gitlab-workhorse.
See merge request !1831
|
| |
| |
| |
| | |
Limiting, if any, should happen in gitlab-workhorse.
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Offloads uploading to GitLab Workhorse
- Use /authorize request for fast uploading
- Added backup recipes for artifacts
- Support download acceleration using X-Sendfile
|
| |
|
|
|
|
| |
Users are allowed to supply namespace%2Fproject instead of a numeric ID
|
|
|
|
| |
This change relies on changes in gitlab_git and gitlab-git-http-server.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this change NGINX would convert a chunked HTTP POST (e.g.
git push) into a HTTP 1.0 single large POST. This creates an
unnecessary delay, and it creates unnecessary memory pressure on
gitlab-git-http-server.
For the response ('proxy_buffering') I am less sure that NGINX 's
buffering behavior is harmful, but it still makes more sense to me
not to interfere with gitlab-git-http-server (and the Golang net/http
server).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://gitlab.com/gitlab-org/gitlab-git-http-server
This change introduces the GITLAB_GRACK_AUTH_ONLY environment
variable. When set, Grack requests to GitLab will only respond with
the user's GL_ID (if the request is OK) or an error. This allows
gitlab-git-http-server to use the main GitLab application as an
authentication and authorization backend.
If we like how this works we should drop the GITLAB_GRACK_AUTH_ONLY
variable at some point in the future.
|
|\
| |
| | |
Use whoami instead of $USER
|
| |
| |
| | |
- Use whoami instead of relying on the existence of $USER enviroment variable which is not always present
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Close #178 Nginx conf default_host documentation
This closes #178
We're just making it clear that some nginx installs such as by default on recent Ubuntu's, the /etc/nginx/sites-enabled/default file will conflict the listen line of the gitlab nginx conf's due to the default_server directive.
changed installation.md to identify the issue to a user
added notes to both nginx configs for gitlab and gitlab-ssl
[ci-skip
See merge request !225
|
| | |
|
| |
| |
| |
| |
| | |
We want to make users aware that the nginx default config will conflict
with the gitlab default_server conf file.
|
| | |
|
| |
| |
| |
| | |
omnibus-gitlab.
|
|\ \
| | |
| | | |
Specify shell while run me as git user
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Some users disabled "git" user's shell after finished installation, this
will lead to "This account is currently not available" and could not
run /etc/init.d/gitlab, this dirty trick fix it.
Signed-off-by: Drunkard Zhang <gongfan193@gmail.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
https://github.com/mattes/gitlabhq into mattes-go-get-workaround-nginx"
This reverts commit 51349ca3c83c56e072f87253d375316f7164b49a, reversing
changes made to b180476bd69bdf99b1727b041116fa8447c0201f.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into mattes-go-get-workaround-nginx
Conflicts:
lib/support/nginx/gitlab
lib/support/nginx/gitlab-ssl
|
| | | |
|