| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | | |
Update installation docs to include Docker, others
See merge request !8943
|
| | | |
| | |
| | |
| | |
| | |
| | | |
As per this comment
https://gitlab.com/gitlab-com/support/issues/374#note_22056587 we're
moving documentation around from the support workflows.
|
| | |/ |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Gitlab from sources : proper utf8mb4 support for MySQL 5.5 to 5.7
See merge request !8508
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
1. Gems need to be installed before we can run the
gitlab:workhorse:install task
1. Update gitlab-shell after gitlab-workhorse since it's a manual step
that needs to be done in `/home/git/gitlab-shell`
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Bump Git version requirement to 2.8.4
Following gitlab-org/omnibus-gitlab!1108, the install doc and README should be updated too.
See merge request !7878
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
|
| |/
|
|
|
|
| |
The task will use the canonical repo and the required version.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
|
| |
v1.0.0 was mistakenly tagged with a lightweight, rather than annotated, tag,
which caused compiled versions of workhorse to wrongly report their version.
|
| |
|
|
|
|
| |
[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
| |
[ci skip]
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add omnibus rake task
## Why was this MR needed?
There was no omnibus example
## Does this MR meet the acceptance criteria?
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
See merge request !5416
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Clarify NGINX config setup
These changes are to clarify that the paths may need to be changed in
the NGINX config file depending on where GitLab is installed.
See merge request !6834
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
users should remove former Go installation folder
## What does this MR do?
It ensure users installing or updating from source will remove their former Go installation folder in `/usr/local/go`, to avoid raising errors that could lead to new issues being created.
## Are there points in the code the reviewer needs to double check?
1. The `rm -rf` should not be verbose if folder does not exists.
1. May a user have some kind of configuration files in this folder ?
## Why was this MR needed?
I did faced the error, that led me to the solution stated here : https://gitlab.com/gitlab-org/gitlab-workhorse/issues/29#note_4155517
gitlab-org/gitlab-workhorse#29
See merge request !6602
|
| | | | | |
|
| | |/ /
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Move reply by email docs to a new location
## What does this MR do?
Move reply by email docs to a new location.
Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/3349
## Moving docs to a new location?
See the guidelines: http://docs.gitlab.com/ce/development/doc_styleguide.html#changing-document-location
- [ ] Make sure the old link is not removed and has its contents replaced with a link to the new location.
- [ ] Make sure internal links pointing to the document in question are not broken.
- [ ] Search and replace any links referring to old docs in GitLab Rails app, specifically under the `app/views/` directory.
- [ ] If working on CE, submit an MR to EE with the changes as well.
See merge request !6517
|
| | | | |
| | | |
| | | |
| | | | |
[ci skip]
|
| | | | |
| | | |
| | | |
| | | | |
Fixes Go 1.5 compatibility.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Update "Installation from source" guide for 8.13.0
Following the steps from https://gitlab.com/gitlab-org/release-tools/blob/master/doc/release-candidates.md#creating-rc1.
See merge request !6565
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
[ci skip]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/ /
| |
| |
| |
| |
| | |
With the introduction of repository storages validations it becomes
necessary to add the flag `SKIP_STORAGE_VALIDATION` to the gitlab-shell
install command, since that command will create the storage paths
|
| | |
| |
| |
| | |
Fixes rejected API git archive extensions; improves Sentry errors.
|
| | |
| |
| |
| | |
This adds (basic) Sentry support.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Security and safety improvements for gitlab-workhorse integration
Companion to https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/60
- Use a custom content type when sending data to gitlab-workhorse
- Verify (using JWT and a shared secret on disk) that internal API requests came from gitlab-workhorse
This will allow us to build features in gitlab-workhorse that require
more trust, and protect us against programming mistakes in the future.
This is designed so that no action is required for installations from
source. For omnibus-gitlab we need to add code that manages the shared
secret.
See merge request !5907
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
