-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
auto-upload documentation from travis #1576
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
Comments
I thought our plan was to ditch our documentation server eventually and start using http://pytest.readthedocs.io, no? |
Using RTD definitely would be the easier solution 😉 |
rtd cant do a regendoc run before the sphinx build |
True, but that doesn't completely prevents us from using RTD... it takes care of all else you mentioned in the issue. Plus RTD is already working, we really only need to implement the proper redirection in the We could automate running regendoc on Travis, but TBH having that as part of the PR for the release seems OK for now. We could certainly improve this later by making Travis run regendoc and pushing that automatically. |
agreed |
Great! Just to reiterate my request on the mailing list, I really would like for someone with Linux and some server admin to implement the redirect on pytest.org... 😟 |
I have access to the server, but it's been years since I last configured an Apache server - I suggest we look at it with @hpk42 at the sprint. |
i also see myself unable to fix the webserver |
Agreed.
IIUC we have to configure the webserver to also redirect pytest.org/latest to pytest.readthedocs.io to keep existing links from breaking, and enable google to now index the new location. |
in order to automatically keep the documentation up2date, we should always build it in one travis job, that will also rsync it to the server for tags
in order to handle credentials it we have the following options
in either case we need to deploy rrsync on the repo as a way to prevent rsync from too much access
The text was updated successfully, but these errors were encountered: