Browse code

HTTPS urls for ./project

Signed-off-by: Eric Windisch <eric@windisch.us>

Eric Windisch authored on 2015/04/12 02:58:09
Showing 4 changed files
... ...
@@ -4,7 +4,7 @@ In the spirit of openness, Docker created a Governance Advisory Board, and commi
4 4
 All output from the meetings should be considered proposals only, and are subject to the review and approval of the community and the project leadership.
5 5
 
6 6
 The materials from the first Docker Governance Advisory Board meeting, held on October 28, 2014, are available at 
7
-[Google Docs Folder](http://goo.gl/Alfj8r)
7
+[Google Docs Folder](https://goo.gl/Alfj8r)
8 8
 
9 9
 These include:
10 10
 
... ...
@@ -47,7 +47,7 @@ To build Docker, you will need the following:
47 47
 * A recent version of Git and Mercurial
48 48
 * Go version 1.3 or later
49 49
 * A clean checkout of the source added to a valid [Go
50
-  workspace](http://golang.org/doc/code.html#Workspaces) under the path
50
+  workspace](https://golang.org/doc/code.html#Workspaces) under the path
51 51
   *src/github.com/docker/docker* (unless you plan to use `AUTO_GOPATH`,
52 52
   explained in more detail below)
53 53
 
... ...
@@ -237,9 +237,9 @@ are as follows (in order):
237 237
   installed at "/usr/bin/docker", then "/usr/bin/dockerinit" will be the first
238 238
   place this file is searched for)
239 239
 * "/usr/libexec/docker/dockerinit" or "/usr/local/libexec/docker/dockerinit"
240
-  ([FHS 3.0 Draft](http://www.linuxbase.org/betaspecs/fhs/fhs.html#usrlibexec))
240
+  ([FHS 3.0 Draft](https://www.linuxbase.org/betaspecs/fhs/fhs.html#usrlibexec))
241 241
 * "/usr/lib/docker/dockerinit" or "/usr/local/lib/docker/dockerinit" ([FHS
242
-  2.3](http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA))
242
+  2.3](https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA))
243 243
 
244 244
 If (and please, only if) one of the paths above is insufficient due to distro
245 245
 policy or similar issues, you may use the `DOCKER_INITPATH` environment variable
... ...
@@ -145,7 +145,7 @@ To test locally:
145 145
 make docs
146 146
 ```
147 147
 
148
-To make a shared test at http://beta-docs.docker.io:
148
+To make a shared test at https://beta-docs.docker.io:
149 149
 
150 150
 (You will need the `awsconfig` file added to the `docs/` dir)
151 151
 
... ...
@@ -341,7 +341,7 @@ git push -f origin docs
341 341
 make AWS_S3_BUCKET=docs.docker.com BUILD_ROOT=yes DISTRIBUTION_ID=C2K6......FL2F docs-release
342 342
 ```
343 343
 
344
-The docs will appear on http://docs.docker.com/ (though there may be cached
344
+The docs will appear on https://docs.docker.com/ (though there may be cached
345 345
 versions, so its worth checking http://docs.docker.com.s3-website-us-east-1.amazonaws.com/).
346 346
 For more information about documentation releases, see `docs/README.md`.
347 347
 
... ...
@@ -14,11 +14,11 @@ we run Docker in Docker to test.
14 14
 
15 15
 Leeroy is a Go application which integrates Jenkins with 
16 16
 GitHub pull requests. Leeroy uses 
17
-[GitHub hooks](http://developer.github.com/v3/repos/hooks/) 
17
+[GitHub hooks](https://developer.github.com/v3/repos/hooks/) 
18 18
 to listen for pull request notifications and starts jobs on your Jenkins 
19 19
 server.  Using the Jenkins [notification plugin][jnp], Leeroy updates the 
20 20
 pull request using GitHub's 
21
-[status API](http://developer.github.com/v3/repos/statuses/)
21
+[status API](https://developer.github.com/v3/repos/statuses/)
22 22
 with pending, success, failure, or error statuses.
23 23
 
24 24
 The leeroy repository is maintained at