<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shiny Server on Barbara&#39;s Journal</title>
    <link>/tags/shiny-server/</link>
    <description>Recent content in Shiny Server on Barbara&#39;s Journal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 Dec 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/tags/shiny-server/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Day 2</title>
      <link>/2017/12/12/day-2/</link>
      <pubDate>Tue, 12 Dec 2017 00:00:00 +0000</pubDate>
      
      <guid>/2017/12/12/day-2/</guid>
      <description>Some things we did  More Shiny Server investigation. Today&amp;rsquo;s issue was related to Shiny Server&amp;rsquo;s built-in monitoring dashboard (basically, an admin app). There are endpoints in Shiny Server&amp;rsquo;s code that serve data which populates the dashboard (including the number of running processes, as well as more details). Here&amp;rsquo;s the Asana task with more details. We couldn&amp;rsquo;t get far with naive debugging and Alan is in the process of trying to get a repro.</description>
    </item>
    
    <item>
      <title>Day 1</title>
      <link>/2017/12/11/day-1/</link>
      <pubDate>Mon, 11 Dec 2017 00:00:00 +0000</pubDate>
      
      <guid>/2017/12/11/day-1/</guid>
      <description>The plan Created a new Asana board with all the tasks Alan and I have on our plate for the immediate future (Barbara &amp;amp; Alan World Domination):
 Asana Board - Day 1   The goal is to get the small things off our plate first (SSOS and SSP release blog posts and SSP support ticket), so we can then invest more focused time into proxyrec, which will be harder.</description>
    </item>
    
  </channel>
</rss>