The `hide_from_sitemap` metadata variable was a custom thing we implemented to add a "noindex" meta-header to pages and to exclude a page from the search auto-complete. However, pages with that option set would still be included in sitemap.xml, resulting in search engines to visit those pages (only to discover they should not index them). This patch replaces the custom `hide_from_sitemap` value for `sitemap: false`, which is a metadata variable that's defined by the "jekyll-sitemap" plugin we use to generate the sitemap.xml; https://github.com/jekyll/jekyll-sitemap/blob/v1.4.0/README.md#exclusions Setting this variable will now: - add a "noindex" metadata header to the page - exclude the page from the sitemap.xml. - exclude the page from /js/metadata.json (used for search autocomplete) Also fixed an issue in the metadata.json where the `notoc` metadata was used to exclude pages, however that variable is meant to disable the in-page TOC (right-hand side navigation with anchor links). Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1.4 KiB
description, keywords, title, sitemap
| description | keywords | title | sitemap |
|---|---|---|---|
| Mount directory from machine | machine, mount, subcommand | docker-machine mount | false |
Mount directories from a machine to your local host, using sshfs.
The notation is machinename:/path/to/dir for the argument; you can also supply an alternative mount point (default is the same dir path).
Example
Consider the following example:
$ mkdir foo
$ docker-machine ssh dev mkdir foo
$ docker-machine mount dev:/home/docker/foo foo
$ touch foo/bar
$ docker-machine ssh dev ls foo
bar
Now you can use the directory on the machine, for mounting into containers. Any changes done in the local directory, is reflected in the machine too.
$ eval $(docker-machine env dev)
$ docker run -v /home/docker/foo:/tmp/foo busybox ls /tmp/foo
bar
$ touch foo/baz
$ docker run -v /home/docker/foo:/tmp/foo busybox ls /tmp/foo
bar
baz
The files are actually being transferred using sftp (over an ssh connection),
so this program ("sftp") needs to be present on the machine - but it usually is.
To unmount the directory again, you can use the same options but the -u flag.
You can also call fuserunmount (or fusermount -u) commands directly.
$ docker-machine mount -u dev:/home/docker/foo foo
$ rmdir foo
Files are actually being stored on the machine, not on the host. So make sure to make a copy of any files you want to keep, before removing it!