Skip to content

Instantly share code, notes, and snippets.

@trestletech
Last active January 4, 2016 04:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save trestletech/8570479 to your computer and use it in GitHub Desktop.
Save trestletech/8570479 to your computer and use it in GitHub Desktop.
Setup Shiny in R 2.15.2 on Ubuntu
sudo apt-get update
# Install the needed compilers to use when building R
sudo apt-get install g++ gcc gfortran -y
# Grab all the dependencies of the R package, but don't actually install it.
sudo apt-get build-dep r-base -y
# Get R 2.15.2 from CRAN
wget http://cran.rstudio.com/src/base/R-2/R-2.15.2.tar.gz
tar -xzvf R-2.15.2.tar.gz
cd R-2.15.2
# Clean up any old build configurations
sudo make clean
sudo make distclean
# Configure like the official .deb is configured
./configure --prefix=/usr \
--with-cairo \
--with-jpeglib \
--with-readline \
--with-tcltk \
--with-system-bzlib \
--with-system-pcre \
--with-system-zlib \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--datadir=/usr/share/R/share \
--includedir=/usr/share/R/include \
--enable-R-profiling \
--enable-R-shlib \
--enable-memory-profiling
# Build (with 4 parallel jobs)
make -j4
# Check the build
make check
# Install the build
sudo make install
cd ..
# Install an older Rcpp compatible with 2.15.2
wget http://cran.r-project.org/src/contrib/Archive/Rcpp/Rcpp_0.10.5.tar.gz
sudo R CMD INSTALL Rcpp_0.10.5.tar.gz
# Install Shiny
sudo su - \
-c "R -e \"install.packages('shiny', repos='http://cran.rstudio.com/')\""
# -*- mode: ruby -*-
# vi: set ft=ruby :
######### Shiny Server Pro OpenLDAP Test VM #############
# This VM is based on a Ubuntu 12.04.3 x64 image. It
# will provision and install OpenLDAP (slapd) with the
# ldap-utils package and add some test data into the
# database. It's configured with the static IP address:
# 10.0.0.14 . There should be no firewall between the
# host and this VM. It requires StartTLS encryption.
# The root login credentials are as follows:
# user: cn=admin,dc=ssp-openldap-tls
# password: LDAPPass
#
# When connecting, you may be prompted to accept an
# invalid SSL certificate. This is expected, as it's
# not signed by a real CA.
#########################################################
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Settings for Vagrant
config.vm.box = "ubuntu-12.04.3-server-amd64"
# If the box isn't already added to vagrant, get it from this URL
config.vm.box_url = "http://rstudio-vagrant-boxes.s3-website-us-west-2.amazonaws.com/boxes/ubuntu-12.04.3-server-amd64.box"
config.vm.host_name = "ubuntu-build-r"
config.vm.provision "shell", path: "setup.sh"
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network "private_network", ip: "10.0.0.65"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network :public_network
# If true, then any SSH connections made will enable agent forwarding.
# Default value: false
# config.ssh.forward_agent = true
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "site.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment