DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH 0/2] Host tarballs on Fastly CDN
Date: Tue, 24 May 2016 00:28:01 +0200	[thread overview]
Message-ID: <1464042483-6954-1-git-send-email-thomas.monjalon@6wind.com> (raw)

Thanks to the help from Fastly (https://www.fastly.com/open-source),
there is now a CDN for dpdk.org.
It is simply a distributed varnish cache with an API and a nice dashboard.

In order to ease understanding of cache behaviour, only the big files
(mainly release tarballs) are cached.
The new domain fast.dpdk.org, hosted by Fastly, mirrors the domain
static.dpdk.org which keeps the same tree as dpdk.org but only for
big static files. There is no HTML file on these domains.
So the domain static.dpdk.org acts as gateway between the full website
origin and the distributed static files. There is no benefit of directly
using static.dpdk.org from your browser, except for website troubleshooting.

Thomas Monjalon (2):
  redirect big static files to the CDN
  add releases page

 about.html        |  4 +--
 content.css       | 23 +++++++++++++++
 doc.html          |  2 +-
 doc/archives.html |  8 ++---
 download.html     |  6 ++--
 rel.html          | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 120 insertions(+), 10 deletions(-)
 create mode 100644 rel.html

-- 
2.7.0

             reply	other threads:[~2016-05-23 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 22:28 Thomas Monjalon [this message]
2016-05-23 22:28 ` [dpdk-web] [PATCH 1/2] redirect big static files to the CDN Thomas Monjalon
2016-05-24 14:34   ` Van Haaren, Harry
2016-05-23 22:28 ` [dpdk-web] [PATCH 2/2] add releases page Thomas Monjalon
2016-05-24 14:34   ` Van Haaren, Harry
2016-05-24 15:52 ` [dpdk-web] [PATCH 0/2] Host tarballs on Fastly CDN Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1464042483-6954-1-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).