Page MenuHomePhabricator

Prepare Phame to support heavy traffic for a Tech Department blog
Open, NormalPublic0 Story Points

Description

Steps to Reproduce (tentative)

  1. Create a new blog entry at https://phabricator.wikimedia.org/phame/blog/{id_number}
  2. Browse to the new blog entry via https://techblog.wikimedia.org/{id_number}

Actual Results
Blog page is served directly from Phabricator.
Blog entry URLs are ugly.

Requested Results
Page is served from Wikimedia CDN cache if possible.
Blog URLs are prettier.

Brandon suggested that, with the creation of a specific URL (subdomain?) particular to Phame, it would be much easier to cache all of this data and reduce the risk that Phabricator is impaired by heavy traffic to a Phame blog post.

We've discussed re-using the old defunct (currently just a redirect) techblog.wikimedia.org as the pretty and cacheable entrypoint. There's some configuration work to do on the phame side, as well as DNS and edge cache support. Probably this public-facing URI will not allow authentication at all (readonly), enforced at the cache layer by stripping Authorization/Cookie headers.

(This task emerged from a discussion of Phame blogging at the SRE offsite.)

Event Timeline

JAufrecht triaged this task as Normal priority.Tue, Jun 18, 6:57 PM
JAufrecht created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
BBlack updated the task description. (Show Details)Wed, Jun 19, 1:25 PM
BBlack added a project: Traffic.
Restricted Application added a project: Operations. · View Herald TranscriptWed, Jun 19, 1:25 PM

If re-using techblog.wikimedia.org, please take care not to break existing urls. The root path would be fine to change as it was always pointing to a mutable post overview. However, the rest of the domain used to be the blog now at blog.wikimedia.org. Urls such as https://techblog.wikimedia.org/2009/07/power-outage-in-wikimedias-european-servers/ currently work and have been used in publications elsewhere, and are expected to continue to work (with redirect).

This could be done in numerous ways of course. The simplest would be to move the redirect we currently have at /* and reduce its scope to only the 2007-2018 paths.

Implementing a blanket redirect to the legacy blog URI for ^/20(0[7-9]|1[0-8])/ should be feasible in VCL or Lua at the edge. Or alternatively, we could also just leave it alone and pick another hostname, too.

ema moved this task from Triage to Caching on the Traffic board.Fri, Jun 21, 8:09 AM
mmodell added a comment.EditedFri, Jun 21, 12:37 PM

This seems like a good idea, however, the upstream documentation has a warning that there are some issues with an external blog / dedicated subdomain: https://secure.phabricator.com/book/phabricator/article/phame/#external-blogs

Nevertheless, I don't think that any issues will be insurmountable...

greg removed mmodell as the assignee of this task.Sat, Jul 6, 5:21 AM
greg moved this task from INBOX to Later / Need volunteer on the Release-Engineering-Team-TODO board.
greg added a subscriber: mmodell.
jijiki added a subscriber: jijiki.Mon, Jul 8, 4:59 PM
ayounsi added a subscriber: ayounsi.Mon, Jul 8, 4:59 PM
CDanis added a subscriber: CDanis.Thu, Jul 11, 4:44 PM
JAufrecht renamed this task from Set up a subdomain for Phame to enable caching to Prepare Phame to support heavy traffic for a Tech Department blog.Wed, Jul 17, 7:01 PM
JAufrecht updated the task description. (Show Details)