You may be interested in deploying your learnr tutorial on shinyapps.io so that students can access them from the web browser.
However, you will need to know how to optimize your application settings so that your tutorials are able to handle a large number of users at once (for example, a 60-person class logging onto the same tutorial to complete interactive exercises during a statistics lecture).
In order to publish your tutorials on
can follow the normal
process of publishing your tutorials from the RStudio IDE to
shinyapps.io. This will not be covered extensively here, as
our main concern is optimizing tutorial performance.
Note that there are other options for hosting tutorials besides
shinyapps.io, such as:
Both of these require some configuration and setup, and may be beyond
what either you or your students wish to undertake at the time (i.e. if
you are running a short-term course). This leads to a third option that
costs money, but may save you valuable time on system administration:
deploying your learnr tutorial on
Note: Currently, the free
service is designed for no more than three to five users at once. If you
would like multiple users to be able to access the service without the
tutorial crashing, you will need to pay for a hosted
As an educator, we assume you have a few concerns:
Balancing these two things will be a part of figuring out your optimal configuration settings.
Once you have published your tutorials to
log into your account, click on the application page and configure the
Then go to
Settings > General and configure the
Finally, go to the Settings > Advanced page and configure the following:
(Instance Size) / (Worker Processes * Max Connections) = Amount of memory available for each new student accessing your tutorial.
We recommend you set the Start Count and Instance Size to the maximum, monitor hours used, and adjust settings from there.
Because you are paying for the active hours of use per month, you will want to minimize this to stay within your subscription limits. To do this, you can adjust any of the following:
A good workflow is to change only one setting, observe usage metrics, and modify as needed.
Suppose you are teaching a statistical programming seminar over 5 weeks for several class sections of 60 people each. The course is short and students have just been introduced to R and RStudio, so it may not be worth setting up a full server for hosting the seminar tutorials or asking students to configure their own R package.
A browser-based interface is also friendly to those who may have trouble understanding or navigating the RStudio interface during their first weeks of classes.
A few sections are back-to-back, so ideally, the settings on learnr tutorials are robust enough to allow the next section’s students to access them.
For my situation, I had my department purchase the Standard
shinyapps.io subscription for $100/month, which gave me
2,000 Active Hours per month. (Note that Active
Hours refers to the amount of time spent launching the tutorial
and actively processing R code and input submitted by students on each
For each tutorial I deployed, I set up:
I then observed my usage metrics in the
Metrics. After noticing that my tutorials did
not require excessive memory, I:
After the 5-week course was done, I:
shinyapps.io Standard subscription,
This enabled students to return to the tutorial after the workshop was done, without being optimized for mass numbers of students accessing the tutorial at once.
We used around 1000 Active Hours in our first month, and around 300 in our second month of the course, so next year, I will likely purchase the Standard subscription (<= 2000 hours / month) for one month, and reduce to the Basic level (<= 500 hours / month) in the second month.
Example of the usage metrics dashboard below:
For consecutive classes, we still had some issues with lingering open
server connections from the previous class getting in the way. I
published an identical learnr tutorial with a different name
"tutorial-2"), so I could direct some students to a
different link as needed.