#readthedocs

Just to make sure i'm not missing it, there's no support for a webhook originating at RTD? E.g. something that'll run whenever docs update?

dstufft: there's code to do it, but we never turned it on becuase it's half done

whats your use case?

presumably it should be the same as your VCS with a small delay

I want to stick a HTTPS terminator in front of RTD, but to save the cost of the origin hop I'm thinking about making it varnish, and then use a web hook to purge the cache :D

sounds like a premature optimization if I've ever heard one :)

though I assume it's fastly so you're wanting the CDNiness?

I need to run -- but it's definitely something that we should support, so thanks for the ping on it :)

ericholscher: sorry I got distracted, yes in this case it's Fastly. Half of that is just because it's one less thing to maintain if I let them handle it :]

dstufft: TWISTED WEB

(okay that's probably not as good as fastly)

glyph: for some things on RTD I probably won't be putting them behind Fastly and sorting out how to do this with Twisted is on my list of things to try, especially once 4888 is done :]

seems to ignore my custom css file

my layout.html template has the line: "{% set bootswatch_css_custom = ['_static/stackato.css'] %}" which puts " <link rel="stylesheet" href="_static/bootstrap-sphinx.css" type="text/css" />" in my locally built docs

missing from the one that's built on readthedocs.org ... not critical, but I'm curious what I'm doing wrong

hmm, possibly related to https://github.com/rtfd/readthedocs.org/issues/... ?

Quick question: When doing code blocks, instead of indenting, can I wrap them, such as how markdown does it (e.g.: ```json)?

fixxxermet: http://sphinx-doc.org/markup/code.html

fixxxermet: e.g. ".. code-block:: json"

fixxxermet: d'oh, I see now that I've probably misunderstood your question

fixxxermet: any particular reason you don't want to use indentation?

ericholscher: something triggered in pingdom, checked it both from my work and from my server to make sure it was accessable and it was so I just cleared the event.

Wraithan: hrm, yea -- I think there was a network blip

NR emailed me about it also

Yah, figured it was a blip or routing issue or something