Skip to content

Latest commit

 

History

History
60 lines (36 loc) · 2.25 KB

README.md

File metadata and controls

60 lines (36 loc) · 2.25 KB
Raw

Teleport Docs

Teleport docs are built using mkdocs and hosted as a bunch of static files in S3.

Look at build.sh script to see how it works.

To Publish New Version

  • Update build.sh.
  • Update theme/scripts.html to add a new version to the docVersions array of versions
  • Create a new YAML file, like 4.3 if you are releasing version 4.3.

Deploying

Teleport docs are published using a private web repository. See web/README.md for more info.

Running Locally

We recommend using Docker to run and build the docs.

make run-docs will run the docs and setup a livereload server for easy previewing of changes.

make docs will build the docs, so they are ready to ship to production.

Tools used to build the Docs

Teleport Docs are made with MkDocs and a few markdown extensions, First time users will need to install MkDocs https://www.mkdocs.org/#installation.

To run the latest version of the docs on http://127.0.0.1:8000:

$ ./run.sh

To run a specific version of the docs:

$ mkdocs serve --config-file 4.3.yaml

Checking for bad links

Install milv (Markdown Internal Link Validator) using go get -u -v github.com/magicmatatjahu/milv.

Change to the appropriate base directory, then run milv and make sure it reports no errors:

$ cd docs/4.1`
$ milv
NO ISSUES :-)

milv will validate all internal and external links by default. The external link checking can take 30 seconds or so to run. You can run milv -v to see all outgoing requests if you think it's taking too long. You can also skip external link checking altogether with milv --ignore-external - this can be useful if you're rapidly trying to fix internal links.

Make sure that you fix any broken links or errors before committing your changes!

If there is a genuine false positive or case where milv is failing to parse a link correctly but it does work (and you have validated this using make run-docs or mkdocs serve) then you can add a whitelist under the appropriate section in milv.config.yaml and commit this back to the repo.