| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
If there is an existing gitlab.yml file with snippets explicitly
disabled, they won't be enabled with this change.
|
|\
| |
| |
| |
| | |
Update storage settings to allow extra values per shard
See merge request !9597
|
| |
| |
| |
| |
| |
| |
| | |
This will be necessary when adding gitaly settings. This version
doesn't make any functional changes, but allows us to include this
breaking change in 9.0 and add the needed extra settings in the future
with backwards compatibility
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix typo in Gitlab application config file
Closes #24998
See merge request !9702
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
Add storage class configuration option for Amazon S3 remote backups
See merge request !9599
|
| |/ |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| | |
# Conflicts:
# db/schema.rb
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|\
| |
| |
| |
| |
| |
| | |
Mattermost slash auto config
Closes #24769
See merge request !8070
|
| |\
| | |
| | |
| | |
| | |
| | | |
# Conflicts:
# config/gitlab.yml.example
# lib/mattermost/session.rb
# spec/lib/mattermost/session_spec.rb
|
| | | |
|
| |/
|/| |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
Code improvements, bug fixes, finish documentation and specs
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/18441
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Send 'admin emails' weekly, not daily
Daily seems to be to spammy, so let's default to weekly instead.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15520
See merge request !3923
|
| |
| |
| |
| | |
Daily seems to be to spammy, so let's default to weekly instead.
|
|/
|
|
|
|
|
|
|
|
| |
These changes were pulled from GitLab EE to support configuring
an alternative API URL than the default https://api.github.com.
In addition, the `verify_ssl` flag allows users to disable SSL cert
checking.
One modification: add a default `args` option if it does not exist
to avoid breaking existing configurations.
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow Omniauth providers to be marked as external
Related to #4009
With this MR we will be able to allow the user to set which Omniauth Providers they would like to have as external. All users login in via these providers will be marked as external, even if they already had an account before. If the provider is removed form the list of external providers, the users will be marked as internal at their next login.
MR for Omnibus: gitlab-org/omnibus-gitlab!727
/cc @dblessing @DouweM
See merge request !3657
|
| | | |
|