Skip to content

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

Closed
RonnyPfannschmidt opened this issue May 31, 2016 · 9 comments
Closed

auto-upload documentation from travis #1576

RonnyPfannschmidt opened this issue May 31, 2016 · 9 comments

Comments

@RonnyPfannschmidt
Copy link
Member

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

  • need to travis encrypt a new ssh keypair and deploy the pubkey to the server
  • ask travis to sponsor a pro account that allows to use ssh keys

in either case we need to deploy rrsync on the repo as a way to prevent rsync from too much access

@nicoddemus
Copy link
Member

nicoddemus commented May 31, 2016

I thought our plan was to ditch our documentation server eventually and start using http://pytest.readthedocs.io, no?

@The-Compiler
Copy link
Member

Using RTD definitely would be the easier solution 😉

@RonnyPfannschmidt
Copy link
Member Author

rtd cant do a regendoc run before the sphinx build

@nicoddemus
Copy link
Member

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 pytest.org server.

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.

@RonnyPfannschmidt
Copy link
Member Author

agreed

@nicoddemus
Copy link
Member

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... 😟

@The-Compiler
Copy link
Member

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.

@RonnyPfannschmidt
Copy link
Member Author

i also see myself unable to fix the webserver
plus i think we should take a look at changing the domain setup instead of the webserver setup?

@nicoddemus
Copy link
Member

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.

Agreed.

plus i think we should take a look at changing the domain setup instead of the webserver setup?

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.

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

3 participants