Docs at http://django-vanilla-views.org/ not up to date

[adamchainz]

I just looked to adding this to a project, I was surprised to read that only Django up to 1.8 is supported on: http://django-vanilla-views.org/#requirements . This isn't the case on the repo, has the documentation build been failing?

[carltongibson]

Hey @adamchainz.

I suspect it's just a mkdocs gh-deploy (or such) — but updating is needed. (Lack of bandwidth...)

I suspect it'd all just work with an update to tox.ini (and the readme). If you want to use your superpowers to bring it up-to-date that would be amazing!

[carltongibson]

i.e. https://travis-ci.org/tomchristie/django-vanilla-views/builds/357418285 (is already 90% what's needed)

[adamchainz]

tox.ini or .travis.yml?

[carltongibson]

Ah, yes. My pet hate. 😄

Alas, the answer is probably both. (But we might argue we don't really need tox locally for development...)

[tomchristie]

Just .travis.yml would be fine. I'd be okay with us dropping tox.

[tomchristie]

I reckon it's worth us bringing this back up to date and getting it under the encode umbrella. https://github.com/encode/

[adamchainz]

Can I do anything to help with move to encode/updating docs?

[adamchainz]

Ok so I figured out changing the docs in #75 , #76, and #77. Currently it relies on running the mkdocs.py script in the repo (not mkdocs the tool, perhaps an early prototype @tomchristie ?) and copying the results over to the gh-pages branch as I did in #77. They're up to date now at least.

@tomchristie can you give me access to the repo settings, then I'll move them to HTTPS using the new free Lets Encrypt on github pages :)

[tomchristie]

@adamchainz I don't think I can do that against a personal repo.
What do you need, just enforcing HTTPS?

Settings currently look like this, I think it means I need to first update the DNS records.

[adamchainz]

Fair enough, yeah you can't make me admin of a personal repo. And yes, it looks like you might need to go through custom domain setup to find some new DNS records to add, so they can LetsEncrypt.

[adamchainz]

I've just updated the docs for the 1.1.0 release.

If you could check "Enforce HTTPS" @tomchristie that'd be neat.

[adamchainz]

@tomchristie I appreciate you're busy - perhaps you could add me as collaborator on the repo so I can do this and not ask you for other things in the future?