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>
* - Added a new topic to describe how to install Desktop on Windows Home machines.
- Update installation instructions on Windows/Mac topics
- Removed references to Toolbox from the Install topics
- Updated the Install pages to add info on the new onboarding tutorial on startup
* Update docker-for-windows/install-windows-home.md
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Update docker-for-windows/install-windows-home.md
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Update docker-for-windows/install-windows-home.md
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Update docker-for-windows/install-windows-home.md
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* move WSL 2 req above Hyper-V reqs
* Add info on purge container data
Co-authored-by: Stefan Scherer <stefan.scherer@docker.com>
* Removed is from line 80
Removed is from line 80 as this is not required
* changed text to link at line 129
changed text to link at line 129 to make it easy for user to navigate
* changed the URL to link
changed the URL to link for easy navigation
* added these before flags in line 186
added these before flags in line 186
Co-Authored-By: Sebastiaan van Stijn <thaJeztah@users.noreply.github.com>
* - Added a new Overview topic for Docker Desktop
- Moved Dashboard up one level and removed OS-specific topics and images from the Mac and Windows directories
* Updated the Desktop TOC
- Moved Install topics above Getting started topic
- Moved Open source licensing up one level
- Removed OS-specific topics
* Fix review comments
The docs refer to the `CURRENT STATE` column, which may not
be visible without scrolling, so tweaking the column-widths
a bit so that it better fits.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This replaces the JavaScript link fix script with a custom plugin,
based on the jekyll-relative-link plugin, and modified so that it
can be used as Liquid "filter".
While it borrows from the jekyll-relative-links plugin, it takes some shortcuts;
- We use the code from jekyll-relative-links plugin to find/extract
links on the page
- Relative links are converted to absolute links, using the path of
the markdown source file that's passed as argument
- After conversion to an absolute link, we strip the ".md" extension;
no attempt is made to resolve the file that's linked to. This is
different from the jekyll-relative-links plugin, which _does_ resolve
the linked file. This functionality could be added in future by
someone who has more experience with Ruby.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This is a follow-up to d4ead1b120,
which removed the datafile for `docker deploy`, but didn't remove
the stub or removed it from the TOC.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Adding `-it` on a "detached" (`-d`) container is needed
if the container's main process expects a TTY attached to keep
running.
It's not needed for a redis container, so we can remove it here
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Jérémie Drouet
Usha Mandya
Sebastiaan van Stijn
Mathieu Champlon
Beni Rupp
Stefan Scherer
Flavien Berwick
Sourabh Shirhatti
Sebastiaan van Stijn
ajay143444
Usha Mandya
何锦余
Ivan Cheban