Require the ruby racer only in production since installing it on dev machines can cause a lot of problems. Hat tip to Jeroen van Baarsen

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Validate and sanitize snippet file name

Fixes #1816

See merge request !1322

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Fix shell commands in shell install

Fixes #1610

See merge request !1320

Dropdown icon not clickable

Fixes #1642 by using `pointer-events` property supported by [modern browsers](http://caniuse.com/#search=pointer-events)

See merge request !1319

Show files named diff

Fixes #1749

See merge request !1318

Add an extra reference to the 'shell commands' guide

The 'shell commands' guide now also has tips on opening/reading files and handling paths.

See merge request !1321

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Enable Markdown preview for issues, merge requests, milestones, and notes

Add security tips about file and paths

These are some extra guidelines to guard against code execution and path traversal.

See merge request !1317

Updated doc/integration/twitter.md, fixed incorrect callback URL

Fixed a typo in the Integration instructions for Twitter OAuth

See merge request !257

(referencing /users/auth/github/callback,
 not /users/auth/twitter/callback)

Speed up omniauth AddIdentityTable migration

https://dev.gitlab.org/gitlab/gitlabhq/issues/1810

See merge request !1315

Unicorn workers

See merge request !1316

Unicorn advice

See merge request !1314

Add 'grace time' behavior to Sidekiq MemoryKiller

The previous iteration of the memory killer did not give 'large'
jobs much of a chance to finish. This caused them to come back after
each restart, leading to another memory-induced shutdown. By adding
some 'grace time' between the moment we detect a memory peak and
the moment we start shutting down, we hope to give Sidekiq a chance
to get whatever causes its memory to grow 'out of its system'.

See merge request !1313

Drop vagrant from issue tracker guidelines

Is this the preferred method of reproducing an issue? If yes, disregard this MR.

\cc @sytses @marin

See merge request !255

Move sidekiq debug docs to development folder