-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate deployment of GitHub pages #3
Comments
@wkillerud You are currently the expert on travis. Do think using travis to push to gh-pages is a good idea? |
Sure, it looks like they have great support for this :) https://docs.travis-ci.com/user/deployment/pages/ |
@kwltrs, can you sort out the dedicated account and new token? I can help with the config if you need :) |
Should we close this issue and create a new one for creating a new dedicated account? This issue seems to be resolved. |
Created #96 to track the remaining work |
The process of building the html documentation and pushing it to the gh-pages-branch needs to be automated. Preferably our CI should be setup to do this. Travis has a write up, that might help: https://docs.travis-ci.com/user/deployment/pages/
npm run build:htdocs
builds the documentation, which ends up indist
.The text was updated successfully, but these errors were encountered: