Netlify reported "mixed content" warnings (which means that the
website contained links to both HTTPS and HTTP URLs.
Those reports were based on some test-files in the "tests" directory;
```
10:08:07 PM: Finished processing build request in 6m14.58941986s
10:09:14 PM: Mixed content detected in: /tests/src/golang.org/x/net/html/charset/testdata/utf-8-bom-vs-meta-content.html
10:09:15 PM: --> insecure link urls:
10:09:15 PM: - http://www.w3.org/TR/html5/syntax.html#the-input-byte-stream
10:09:15 PM: --> insecure script urls:
10:09:15 PM: - http://w3c-test.org/resources/testharness.js
10:09:15 PM: - http://w3c-test.org/resources/testharnessreport.js
10:09:15 PM: Mixed content detected in: /tests/src/golang.org/x/net/html/charset/testdata/utf-8-bom-vs-meta-charset.html
10:09:15 PM: --> insecure link urls:
10:09:15 PM: - http://www.w3.org/TR/html5/syntax.html#the-input-byte-stream
10:09:15 PM: --> insecure script urls:
10:09:15 PM: - http://w3c-test.org/resources/testharness.js
10:09:15 PM: - http://w3c-test.org/resources/testharnessreport.js
```
We already look to be excluding that directory from our Dockerfile, but
possibly Netlify uses the source itself for this detection, so adding
`tests` to the `exclude` list in the Jenkyll configuration.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Having this variable set causes redirects to always redirect to
https://docs.docker.com, which makes it not possible to preview
redirects locally, or to host them on a different domain (e.g.
on a staging domain).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* DTR release notes for March 2020 Amberjack patch release
* updating dtr and ucp product versions and links to tarballs
* fixing typo
Co-authored-by: Dawn W Docker <dawn.wood@users.noreply.github.com>
Docker Enterprise actively supports the 17.06, 18.03, 18.09, and
19.03 versions, with 17.06 and 18.03 reaching EOL soon.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Simplified EE variables in _config (#9260)
Before we had 2 UCP configuration variables. 1 for pages under "ee" and
1 for pages under "ee/ucp". We had the same pattern for DTR. THis commit
removes the variable at the ee/ucp level, in the hope that all files
will take it from the /ee variable.
* Added Offline Bundles and Bumped Config
* Release notes for patch 19.03.1
Signed-off-by: Adrian Plata <adrian.plata@docker.com>
* Release notes for patch 19.03.1
Signed-off-by: Adrian Plata <adrian.plata@docker.com>
* Release notes for patch 19.03.1
Signed-off-by: Adrian Plata <adrian.plata@docker.com>
* Use site parameter to use latest compose file versions in examples
Make sure that examples use the latest version of the compose file
format, to encourage using the latest version, and to prevent
users from running into "not supported by this version" problems
when copy/pasting, and combining examples that use different
versions.
Also add a note about `version: x` not being equivalent to
`version: x.latest`.
Note that there are still some examples using fixed versions
in the UCP sections; we need to evaluate those to make sure
the right (and supported) versions are used for UCP (which may
be different than "latest").
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Address some v3/v2 issues, and YAML syntax error
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Minor edit
* Final updates
- Added note around v2 and v3 versioning
- Updated note for v3 to match the v2 update
Ulysses Souza