Reputation: 9192
How exactly do I automatically deploy my Mkdocs documentation in Travis CI?
Upvotes: 7
Views: 2314
Reputation: 9192
Here's how to automatically deploy your mkdocs document. Simply follow the 3 steps below.
Simply insert the following code snippets into their respective locations in your .travis.yml
configuration file:
language: python # Set the build language to Python
python: 3.8 # Set the version of Python to use
branches: master # Set the branch to build from
install:
- pip install mkdocs # Install the required dependencies
script: true # Skip script (Don't use this if one already exists)
before_deploy:
- mkdocs build --verbose --clean --strict # Build a local version of the docs
deploy: # Deploy documentation to Github in the gh_pages branch
provider: pages
skip_cleanup: true
github_token: $github_token
local_dir: site
on:
branch: master
If you are using a mkdocs theme that is not mkdocs
or readthedocs
then follow the following steps to install it:
Scenario 1: The theme is installable via pip (such as mkdocs-material)
pip install mkdocs
with the other packages you need to install for example with mkdocs-material
it would be pip install mkdocs mkdocs-material pymdown-extensions pygments
Scenario 2: The theme is not installable via pip (such as docskimmer)
Remove the --strict
argument from mkdocs build --verbose --clean --strict
to suppress a possible error from using theme not installable via pip.
Add the code required to set up the theme in the before_deploy
section, above mkdocs build --verbose --clean
The code in the before_deploy
section would look like this for docskimmer:
before_deploy:
- git clone https://github.com/hfagerlund/mkdocs-docskimmer.git # Clone the repo hosting the code
- cp -r $PWD/mkdocs-docskimmer/mkdocs_docskimmer . # Copy the required code to the repo root
- cp -r $PWD/mkdocs-docskimmer/mkdocs_docskimmer/. ./docs # Copy the required code to the docs folder
- mkdocs build --verbose --clean # Build a local version of the docs
Installation of themes not available via pip may vary.
The final step is to tell Travis CI the credentials required to sign in to your GitHub account to push the changes:
public_repo
scope, skip to step 11Token description
, choose a name for your token - it could be anything; I'd name it something like Travis CI
as you can reuse the token for as many repositories as you like.public_repo
and repo_deployment
scope/permissionGenerate token
at the bottom of the pagegithub_token
<THE TOKEN YOU JUST GENERATED>
No
add
You're done! Please feel free to ask me any questions in the comments.
Also, if the method stops working or doesn't work, PLEASE tell me in the comments and I will fix it ASAP.
Upvotes: 15
Reputation: 534
Its very simple to deploy your MkDocs website using Travis (considered you are using material theme)
Step 1: Create the repository for your project with empty 3 branches called master, dev, gh-pages.
Step 2 : Clone repository and local and checkout to dev branch. Add your MkDocs website to your dev branch on local. Add '/site' directory to git-ignore.(ie don't push .html) add .travis.yml given below in repo. Push you site to dev branch.
Step 3: Raise pull request to master from dev branch
Step 4: Login to Travis and connect your repositories there, Add env variable 'git_token' in travis(used in .travis.yml) its value you can get from github.com -> settings-> dev settings -> personal access token.
Step 5: Complete/Merge pull request to master.It will trigger web-hook and Travis will start build.After build your generated html files will be pushed to gh-pages branch.
Step 6: Go to repository settings and setup git-hub pages website to load from gh-pages branch.
Done
.travis.yml
language: python # Set the build language to Python
python: 3.6 # Set the version of Python to use
branches: master # Set the branch to build from
install:
- pip install mkdocs mkdocs-material pymdown-extensions pygments # Install the required dependencies
script: true # Skip script (Don't use this if one already exists)
before_deploy:
- mkdocs build --verbose --clean --strict # Build a local version of the docs
deploy: # Deploy documentation to Github in the gh_pages branch
provider: pages
skip_cleanup: true
github_token: $github_token
local_dir: site
on:
branch: master
Upvotes: 0