From d984f8c6dfd95c2069c1e924082f75012132d57f Mon Sep 17 00:00:00 2001 From: Jose Gracia Date: Fri, 31 May 2024 11:59:04 +0200 Subject: [PATCH] Add frontmatter --- guides/Best_practice--Connecting_Hawk_to_the_world.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/guides/Best_practice--Connecting_Hawk_to_the_world.md b/guides/Best_practice--Connecting_Hawk_to_the_world.md index 64e8907..7510613 100644 --- a/guides/Best_practice--Connecting_Hawk_to_the_world.md +++ b/guides/Best_practice--Connecting_Hawk_to_the_world.md @@ -1,5 +1,14 @@ # Best Practice -- Connecting Hawk to the world +Change history: + - Initial version ; Jose Gracia, 15 May 2024 + +TODOs: + - Add use-cases for e.g. SVN, R, etc. + - Do we recommend [setting `https_proxy` variables in `.bashrc`](#httpshttp-proxy-variables)? + - Do we recommend [one of the git remote repo protocols](#using-proxy-with-git), i.e. SSH or HTTP, over the other? + + Hawk is surrounded by a strict outgoing firewall. Users can not open arbitrary connections to hosts on the internet. Connections can only be established through a proxy host. This document describes how to set up a proxy, and how to use this proxy in a number of common use cases. Common use cases include: