| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add Irker service configuration options
### What does this MR do?
This MR makes a number of hard-coded Irker parameters configurable in the service settings: Irker server host, port, and default IRC URI. It also removes the "max recipient" limit since the recipient list is configurable only by the project owner, and it makes no sense to update the limit when it is implied in the recipient list already.
### Why was this MR needed?
The existing service assumed that gitlab.com was running an Irker daemon on `localhost` when it was not. Using Irker on gitlab.com thus did not work at all. This MR allows users to provide their own Irker daemons.
### Are there points in the code the reviewer needs to double check?
My main concern is whether allowing a user to specify the server/port combination would have security implications for a host. Given that HipChat and Slack allow users to do this, I didn't think this was doing anything novel.
### What are the relevant issue numbers?
* Closes #1713
* Closes #1714
* Closes gitlab-com/support-forum#139
### Screenshots
### Before
![image](https://gitlab.com/stanhu/gitlab-ce/uploads/2eb3eb815e249e9fb669fc97ecd4f3c8/image.png)
### After
![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/cceaba951c05bd3df2c842cc68046b87/image.png)
See merge request !930
|
| | |
| | |
| | |
| | |
| | |
| | | |
Closes #1713
Closes #1714
Closes gitlab-com/support-forum#139
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Improve documentation of lists in Markdown
See merge request !899
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change RC/final package release timing
Creating the packages one day before the release feels strange, especially in a month like this (June 2015) where the release is on a Monday.
I think it is better to have one more RC.
See merge request !1873
|
| | | | |
|
|\ \ \ \ |
|
| | |_|/
| |/| | |
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
added new doc "command line commands"
Added new doc to GitLab Basics
See merge request !1880
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
git status
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | | |
warnings when using omnibus packages.
|
|/ / /
| | |
| | |
| | | |
Without this link, the SAML docs are hard to discover.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
added info about GitHub importing
Added info that importing doc also works for GitHub EE.
https://dev.gitlab.org/gitlab/gitlabhq/issues/2410#note_49396
See merge request !1878
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
Add 2FA status to user admin API
This MR adds the `two_factor_enabled` field to the admin's API to indicate whether a given user has enabled 2FA.
See merge request !881
|
| | |
| | |
| | |
| | | |
Closes https://github.com/gitlabhq/gitlabhq/issues/9391
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create SSH keys document
@job I created the next document for your review, which is "Creating your SSH Keys"
Thanks!
See merge request !1875
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/875
Provide help for people who aren't SSH-clued by indicating
how to point to key files that have been named something
other than the default. A lot of people seem to assume that
the filename they choose is irrelevant and then wonder why
their private key is not being found by simple 'ssh' commands.
|
| | |/
| |/|
| | |
| | | |
omnibus installations
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Starting shell document to GitLab basics
I added a new branch for all the changes on this MR https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1863
Everything should look nicer now :)
See merge request !1869
|
| | | | |
|