diff options
| author | kwadronaut <kwadronaut@leap.se> | 2013-09-18 01:08:29 +0200 |
|---|---|---|
| committer | kwadronaut <kwadronaut@leap.se> | 2013-09-18 01:08:29 +0200 |
| commit | 31aea109f41dbbe2b4cfbb84ad7da73caa7b9ba8 (patch) | |
| tree | 6a7c0d533b6204d4ee4391ffc1572a4ca24947ac /docs/platform/en.md | |
| parent | 39c11f38953883de4455b49f10e976efc680968a (diff) | |
Replace git: with https: access for git repos (fixing #3689)
Diffstat (limited to 'docs/platform/en.md')
| -rw-r--r-- | docs/platform/en.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/platform/en.md b/docs/platform/en.md index bdae463..f1a1fc1 100644 --- a/docs/platform/en.md +++ b/docs/platform/en.md @@ -20,7 +20,7 @@ LEAP maintains a repository of platform recipes, which typically do not need to As these recipes consist in abstract definitions, in order to configure settings for a particular service provider a system administrator has to create a provider instance (see below). -LEAP's platform recipes are distributed as a git repository: `git://leap.se/leap_platform.git` +LEAP's platform recipes are distributed as a git repository: `https://leap.se/git/leap_platform` The provider instance --------------------- @@ -64,7 +64,7 @@ One other significant difference between LEAP and typical system automation is h These two approaches, masterless push and pre-compiled static configuration, allow the sysadmin to manage a set of LEAP servers using traditional software development techniques of branching and merging, to more easily create local testing environments using virtual servers, and to deploy without the added complexity and failure potential of a master server. -The `leap` command line tool is distributed as a git repository: `git://leap.se/leap_cli`. It can be installed with `sudo gem install leap_cli`. +The `leap` command line tool is distributed as a git repository: `https://leap.se/git/leap_cli`. It can be installed with `sudo gem install leap_cli`. Getting started ---------------------------------- |