Skip to main content

Quick guide to install Shiny Server (Open Source Edition)

Shiny Server (https://www.rstudio.com/products/shiny/shiny-server/) is a server to put Shiny (http://shiny.rstudio.com/) applications or interactive documents available over the web. The official documentation seems quite confusing to me, so I want to share this quick tutorial for people approaching it for the first time.
The procedure explained in this post has been tested and replicated on several Linux Red Hat Servers 6.6+ 64-bit, but it should work on any Linux distribution that allows RPM management. The overall procedure could be of course automated, but for better understanding of this tutorial I am going to describe any manual step involved.

Installation
Connect to your Linux server as root and download the latest RPM for your specific architecture:

wget https://download3.rstudio.org/centos5.9/x86_64/shiny-server-1.4.0.721-rh5-x86_64.rpm

and then install it using yum:

yum install --nogpgcheck shiny-server-1.4.0.721-rh5-x86_64.rpm

At the end of the installation process you should see an output like this:

Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : shiny-server-1.4.0.721-1.x86_64                                                                                                                 1/1
Creating group shiny
Creating user shiny
shiny-server start/running, process 56680
  Verifying  : shiny-server-1.4.0.721-1.x86_64                                                                                                                 1/1

Installed:
  shiny-server.x86_64 0:1.4.0.721-1


The server will be installed in the /srv/shiny-server/ directory. It is installed as a service and it is up and running at the end of the installation. The installer creates also a new dedicated user called shiny.

R installation.
Shiny is based on R. So now you need to install the R environment (compiling its source code) for the shiny user. Switch to this user:

su shiny

and download the latest R source code:

wget http://ftp.heanet.ie/mirrors/cran.r-project.org/src/base/R-3/R-3.2.1.tar.gz

Extract the downloaded archive:

tar xzvf R-3.2.1.tar.gz

Move to the source code directory and start the configuration for the particular system where you're installing on:

cd R-3.2.1
./configure

and finally build it:

make

At the end of the build process test that it was really successful:

make check

Shiny and R Markdown installation.
Shiny framework and R Markdown come as R packages. Execute the R console as shiny user:

/home/shiny/R-3.2.1/bin/R

and install them the usual way for the R packages:

install.packages("shiny")
install.packages("rmarkdown")

The two commands above download, build and install their dependencies as well.

Exit the R console at the end:

q()

Configuration.
In order to have the Shiny Server using the proper R environment you need to specify it in the upstart configuration file. Open it in editing:

su root
nano /etc/init/shiny-server.conf

and add the following variable:

env R=/home/shiny/R-3.2.1/bin/R

Stop and start the server:
stop shiny-server
start shiny-server

Check the it is up and running opening the following page in a web browser:

http://<hostname>:3838/

You should see a static HTML page like this:

hosting a Shiny demo web application on the upper right corner and a R markdown demo document on the lower right corner:






If the port 3838 (default for the Shiny Server) is busy on your system you could change it editing the server general configuration file /etc/shiny-server/shiny-server.conf

Comments

  1. I have read your blog and I gathered some needful information from your blog. Keep update your blog. Awaiting for your next update.

    weblogic server tutorial

    ReplyDelete
  2. Whatever We Are Gathering the information from the blogs,we have to keep on updating it,Walk In Clinic in Chicago.By getting them into one place.Really thanks for posting.Very Thankful for the Informative Post.

    ReplyDelete
  3. Good Post! , it was so good to read and useful to improve my knowledge as an updated one, keep blogging. After seeing your article I want to say that also a well-written article with some very good information which is very useful for the readers....thanks for sharing it and do share more posts like this.
    AWS Online Training
    Online AWS Certification Training

    ReplyDelete

Post a Comment

Popular posts from this blog

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You