summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcel Amirault <mamirault@gitlab.com>2019-09-05 08:54:33 +0900
committerMarcel Amirault <mamirault@gitlab.com>2019-09-05 08:59:08 +0900
commit077698a328f7270eab3237aa44e5f6523ba07519 (patch)
tree3b9ed6f6df97346beb988f26d95d5a7584b64f1c
parent0fad0ed864c5b0f65956d1794cee2f9bd7bfa608 (diff)
downloadgitlab-ce-docs-serveo-link.tar.gz
Change serveo link as it often goes downdocs-serveo-link
-rw-r--r--doc/development/integrations/jira_connect.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/development/integrations/jira_connect.md b/doc/development/integrations/jira_connect.md
index e1350b02262..9ac87a17232 100644
--- a/doc/development/integrations/jira_connect.md
+++ b/doc/development/integrations/jira_connect.md
@@ -10,8 +10,10 @@ The following are required to install and test the app:
For the app to work, Jira Cloud should be able to connect to the GitLab instance through the internet.
- To easily expose your local development environment, you can use tools like [serveo](https://serveo.net) or [ngrok](https://ngrok.com).
- These also take care of SSL for you because Jira requires all connections to the app host to be over SSL.
+ To easily expose your local development environment, you can use tools like
+ [serveo](https://medium.com/@osanda.deshan/how-to-forward-my-local-port-to-public-using-serveo-4979f352a3bf)
+ or [ngrok](https://ngrok.com). These also take care of SSL for you because Jira
+ requires all connections to the app host to be over SSL.
> This feature is currently behind the `:jira_connect_app` feature flag