summaryrefslogtreecommitdiff
path: root/config.yml.example
Commit message (Collapse)AuthorAgeFilesLines
* Be more consistent about default gitlab_urlremove-trailing-slashesJacob Vosmaer2015-12-111-1/+1
|
* Remove trailing slashes from gitlab_urlJacob Vosmaer2015-12-111-5/+5
| | | | | They do not play nice with gitlab-workhorse (or rather Golang net/http DefaultServemux).
* Add support to connect gitlab-shell to Unicorn via UNIX socketKirill Smelkov2015-11-101-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is well known that UNIX sockets are faster than TCP over loopback. E.g. on my machine according to lmbench[1] they have ~ 2 times lower latency and ~ 2-3 times more throughput compared to TCP over loopback: *Local* Communication latencies in microseconds - smaller is better --------------------------------------------------------------------- Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP ctxsw UNIX UDP TCP conn --------- ------------- ----- ----- ---- ----- ----- ----- ----- ---- teco Linux 4.2.0-1 13.8 29.2 26.8 45.0 47.9 48.5 55.5 45. *Local* Communication bandwidths in MB/s - bigger is better ----------------------------------------------------------------------------- Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem UNIX reread reread (libc) (hand) read write --------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- ----- teco Linux 4.2.0-1 1084 4353 1493 2329.1 3720.7 1613.8 1109.2 3402 1404. The same ratio usually holds for servers. Also UNIX sockets, since they reside on filesystem, besides being faster with less latency, have one another nice property: access permissions to them are managed the same way access to files is. Because of lower latencies and higher throughput - for performance reasons, and for easier security, it makes sense to interconnect services on one machine via UNIX sockets and talk via TCP only to outside world. All internal services inside GitLab can talk to each other via UNIX socket already and only gitlab-shell was missing support to talk to Unicorn via UNIX socket. Let's teach gitlab-shell to talk via UNIX sockets. [1] http://www.bitmover.com/lmbench/ ~~~~ In this patch we - add URI::HTTPUNIX to handle http+unix:// URI scheme - add Net::HTTPUNIX to handle "connect via unix socket and then talk http" - adjust GitlabNet#http_client_for() accordingly - adjust documentation in config.yml.example The http+unix:// scheme is not reinvented anew: the idea about its structure is quite logical an was already established at least in requests-unixsocket python package: http://fixall.online/theres-no-need-to-reinvent-the-wheelhttpsgithubcommsabramorequests-unixsocketurl/241810/ https://github.com/msabramo/requests-unixsocket
* Add a note that changing example configuration files requires changing ↵note_in_configMarin Jankovski2015-06-111-0/+5
| | | | omnibus-gitlab.
* Merge pull request #212 from jirutka/patch-1Dmitriy Zaporozhets2015-04-101-0/+4
|\ | | | | Allow to configure location of the secret file
| * Allow to configure location of the secret fileJakub Jirutka2015-02-081-0/+4
| |
* | Add note about centos for git-annex.Marin Jankovski2015-02-201-0/+1
| |
* | Add a comment about gitlab-shell.Marin Jankovski2015-02-201-0/+2
| |
* | Disable git-annex by defaultDmitriy Zaporozhets2015-02-161-1/+1
| |
* | Add config option to disable git-annexDmitriy Zaporozhets2015-02-161-0/+5
|/
* Merge pull request #172 from bbodenmiller/patch-1Dmitriy Zaporozhets2014-09-261-0/+1
|\ | | | | add note about other HTTPS setup details
| * add note about other HTTPS setup detailsBen Bodenmiller2014-08-231-0/+1
| |
* | Connect to Redis via sockets by defaultJacob Vosmaer2014-09-161-3/+3
| |
* | support using custom redis database, fixes #173Tao2014-09-131-0/+1
| |
* | Merge pull request #141 from attiks/support-redis-passwordDmitriy Zaporozhets2014-09-111-0/+1
|\ \ | |/ |/| added support for redis password
| * added support for redis passwordPeter2014-03-211-0/+1
| |
* | Mention Unicorn on a domain socket as an exceptionJacob Vosmaer2014-06-201-1/+2
| |
* | Use a default for gitlab_url that usually worksJacob Vosmaer2014-06-201-1/+4
|/
* More detailed warning about symlinks in repos_pathJan Schlüter2013-09-171-1/+3
|
* Update config.yml.example for grammarDavid Southard2013-06-121-1/+1
|
* Merge pull request #56 from smashwilson/36-loggerDmitriy Zaporozhets2013-06-101-0/+11
|\ | | | | Logger
| * Oops, Travis doesn't like absolute paths in the config file.ash2013-05-181-1/+2
| |
| * Allow administrators to log users by key id (faster) or by username (clearer).ash2013-05-181-0/+5
| |
| * Add logging-related keys to the example config. Use the same default for both.ash2013-05-181-0/+5
| |
* | Add ca_file/ca_path configuration options.Akinori MUSHA2013-06-071-0/+2
|/
* Add message that repes_path should be real pathmcfedr2013-04-221-0/+1
| | | In the main gitlab config there is a message that this should be the real path, meaning it looks like it can be the symlinked path in this config, experience shows this is not the case.
* Forgot to update config.yml.example with socket directive... Fixed.GitLab2013-04-091-0/+1
|
* Added remote redis support to gitlab_update.rbChris2013-03-291-0/+8
|
* http_settings configuration option added.Akzhan2013-03-231-1/+6
| | | | | | | Now it supports: * self_signed_cert option to allow self-signed certificates over https protocol. * user and password options to pass though http auth.
* add check binDmitriy Zaporozhets2013-02-051-0/+7
|
* gitlab-url configDmitriy Zaporozhets2013-02-051-0/+1
|
* add/remove keys to authorized_keysDmitriy Zaporozhets2013-02-031-0/+1
|
* gitlab-shell base implementationDmitriy Zaporozhets2013-02-031-0/+2
View Lorry Controller Status