Skip to content
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

Proposed role: debops.rtfd #319

Open
ypid opened this issue Nov 6, 2016 · 2 comments
Open

Proposed role: debops.rtfd #319

ypid opened this issue Nov 6, 2016 · 2 comments

Comments

@ypid
Copy link
Member

ypid commented Nov 6, 2016

As it seems to me that we now hit the build time limit on readthedocs.org I would suggest we write a role to self host our own read-the-docs service.
Anyone wants to do it? This is kind of urgent.

Ref: https://read-the-docs.readthedocs.io/en/latest/install.html
Obsoletes proposal: debops.sphinx
Related to: debops/docs#147

@drybjed
Copy link
Member

drybjed commented Nov 6, 2016

Sounds like the role could be based on the debops.netbox role which deploys Python application using virtualenv.

@ypid
Copy link
Member Author

ypid commented Feb 23, 2017

I have just been playing with GitLab and this could also be solved with using GitLab CI. The docs get build currently during CI anyway (Travis CI). Using GitLab artifacts and GitLab Pages, it is pretty easy to set it up so that in the test stage the docs get build and only if that succeeds, the docs get deployed. I actually quite like this approach. Also because then the docs are only build once. No redundant builds and we already have the roles for GitLab :)

Example: https://gitlab.com/ypid/hc (Check the coverage report)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants