Cross-posting this cool blog post about how the Discovery Analysis team
'puppetized' the dashboard backend and learned a ton in the process:
Product Manager, Discovery
---------- Forwarded message ----------
From: Mikhail Popov <mpopov(a)wikimedia.org>
Date: Mon, Aug 21, 2017 at 12:14 PM
Subject: Re: [discovery] Puppetized Discovery Dashboards and Shiny Server
module for Puppet
To: A public mailing list about Wikimedia Search and Discovery projects <
The blog post describing the dashboard Puppetization process just went
up. It explains Puppet and includes tips & resources for learning Puppet
for non-Ops people. If you've been curious about the technology, I
recommend you check out the post.
On Tue, Jun 20, 2017 at 12:16 PM, Mikhail Popov <mpopov(a)wikimedia.org>
Happy to report that production and development sets of Discovery
Dashboards are up and running again, this time managed by Puppet. (There
was a bug with web proxies and DNS settings that delayed this
announcement.) Theoretically they should be snappier to use now because
there is no longer an extra virtualization (Vagrant) layer and they are
running directly on Labs instances.
R is a software and programming language mainly used for statistical
inference, machine learning, and data wrangling & visualization. RStudio's
Shiny is a framework for developing web applications in R, and it's what
Discovery's dashboards are written in.
The Reading::Discovery::Analysis team (with guidance and help from
Guillaume Lederrey) is proud to announce a new module available in Ops'
Puppet repo: shiny_server, which installs & configures RStudio's Shiny
Server for serving R/Shiny applications. The module also provides
resources for installing R packages from CRAN, GitHub, and other remote git
repositories like Gerrit. For a practical example, refer to Discovery
Dashboards base and production profiles.
Mikhail on behalf of Discovery Analysts
Discovery mailing list