Good evening, please can I get the PDF note?
On Feb 12, 2019 10:17 AM, "Adam Johnson" wrote:
> Hi Edward,
> You probably want the Django "start" page: https://www.
> Emailing this mailing list of more than 10,000 addresses for such help is
> not appropriate. It is
The django documentation can be downloaded as PDF by following the link on
the right of its index page: https://docs.djangoproject.com/en/2.1/
On Wed, 13 Feb 2019 at 08:48, Edward Victorhez
> Good evening, please can I get the PDF note?
> On Feb 12, 2019 10:17 AM, "Adam Johnson"
Personally, I depend on this behaviour, but it's only because I'm aware of
it. Others would be too though, so we can't just make that change (not that
you're suggesting that approach).
One approach I think could be good would be:
Consider AWS's cloudfront then :)
El martes, 12 de febrero de 2019, 2:34:09 (UTC-5), Florian Apolloner
> Especially cloudflare is a service we do not want to use. as for the docs
> only, does the mirror on rtd work better for you? They are probably behind
> a CDN.
I’ve been hearing that there are other CDN providers that offer a very
comparable service for a fraction of the cost of CloudFront.
Anyways, at this stage let’s not get bogged down on provider decisions. I’m
curious if anyone has any general objections to a CDN of any kind.
It shouldn’t be that
I would highly recommend cloudflare. It's free, can be set up in 15 minutes
and works really, really well.
On Thu, 14 Feb 2019, 00:36 Cristiano Coelho,
> Consider AWS's cloudfront then :)
> El martes, 12 de febrero de 2019, 2:34:09 (UTC-5), Florian Apolloner
to elaborate on what Tobias said: we deliberately have the infrastructure
spread across multiple service providers: DNS registry, nameservers, hosting,
TLS certificate authority, … None of them have access to everything. The reason
is that we offer the download of the release artifacts
For me it's the trust factor (allowing someone else to decrypt and
re-encrypt all our data). This may be less of an issue for the docs site,
*if* we don't have to assign DNS authority for the whole domain to the CDN
On Wed, Feb 13, 2019, 7:47 PM Kye Russell I’ve been hearing
This very issue of a not-null constraint causes a problem with
django-silk. I'm not sure this matters in practice, because the usage of
django silk is usually for development; I just added an sqlite3 database
alias and a router for django-silk. However, it validates the problem of
Why do we not want to use Cloudflare?
FWIW I agree that the docs site performance is not great (also from
melbourne) - but I'd still suffer the performance hit over going via RTD
mirrors for familiarity.
On Tuesday, 12 February 2019 18:34:09 UTC+11, Florian Apolloner wrote:
I agree that 2 makes sense and isn't a huge usability issue. It looks like
the PR is ready to go whenever this is
On Monday, January 14, 2019 at 5:29:18 PM UTC-5, Adam Johnson wrote:
> I agree with your reasoning, and also favour
On Wednesday, February 13, 2019 at 11:25:37 PM UTC+1, Josh Smeaton wrote:
> Why do we not want to use Cloudflare?
Last time I checked (if one puts the full site behind cloudflare) you'd
have nasty checks that usually triggers captchas for Tor users etc. From
what I can tell there was no
Mail list logo