To be able to build the docs the libraries in docs/doc-requirements.txt
need to be installed. As such, the installation of these libraries
should be part of the setup of the developer virtual env.
Hi, I ran into
`jupyter-repo2docker https://github.com/.../ --ref 16c6b...f1a9f` still using master and ignoring my `--ref`.
@betatim suggested https://gitter.im/jupyterhub/binder?at=5bc05a19c7bf7c3662f9e0bf to
```
have you tried changing the order of the arguments repo2docker --ref 16c...1a9f https://github.com/... we've had issues with the arguments after the URL being interpreted as the command to run in the container
```
which indeed fixed the issue. I am here updating the usage.rst document, where I got the ordering from. Not sure if that is the only documentation showing this order, and also not fixing the issue mentioned by Tim. Yours, Steffen
The `contents::` directive in Sphinx causes the headers of referred
sections to become links back to the line in the table of
contents. This causes the headers to use the default attributes for
links, including underlines. The latter makes the header style out of
line with the rest of the documentation. A single `text-decoration:
none` in the custom CSS file fixes this (note: only for H2 headers
currently: these were the offending ones).
The dockerfile test is used by test_editable, but should not be used
by the generated tests. Removing the verify script will prevent it
being run as part of the generated tests.
This will test whether an externally (host) created file is seen
inside the container. This means starting the container, creating a
temporary file on the host, then running a simple verification command
(`ls`) to detect the file. Once the temporary file is removed on the
host side, it should be removed in the container as well.
This test only verifies the option one way: a change inside the
container (a new file) is reflected in the local host repository
outside the container.
A further test where a modification at the host level is reflected in
the container, is still neede.
This adds an option to run from a local repository in edit mode, where
changes in a running Docker container (for example, through a
notebook) are reflected in the local repository.
Implements the feature suggested in #357
Adds test for the use of a clone depth of 1 for cases where no refspec
is used. This relies on an external source (an existing test
repository), so may break easier.
Stops and starts emphasis around an inline code markup.
Also removes two emphasis sections, since these are at the start of
bullet points, creating emphasis already.
Tim Head