Heroku buildpack: R
R is ‘GNU S’, a freely available language and environment for statistical computing and graphics which provides a wide variety of statistical and graphical techniques: linear and nonlinear modelling, statistical tests, time series analysis, classification, clustering, etc. Please consult the R project homepage for further information.
CRAN is a network of ftp and web servers around the world that store identical, up-to-date, versions of code and documentation for R.
NOTE - Heroku
For the Heroku
cedar-14 stack, please use the cedar-14 branch.
You can specify
cedar-14 branch in the buildpack url as follows:
$ heroku create --stack cedar-14 --buildpack http://github.com/virtualstaticvoid/heroku-buildpack-r.git#cedar-14
$ ls init.r prog1.r prog2.r ... $ heroku create --stack cedar --buildpack http://github.com/virtualstaticvoid/heroku-buildpack-r.git $ git push heroku master ... -----> Heroku receiving push -----> Fetching custom buildpack -----> R app detected -----> Vendoring R x.xx.x Executing init.r script ... -----> R successfully installed
The buildpack will detect your app makes use of R if it has the
init.r file in the root.
The R runtime is vendored into your slug, and includes the gcc compiler for fortran support.
To reference a specific version of the build pack, add the Git branch or tag name to the end of the build pack URL.
$ heroku create --stack cedar --buildpack http://github.com/virtualstaticvoid/heroku-buildpack-r.git#master
Installing R packages
During the slug compilation process, the
init.r R file is executed. Put code in this file to install any packages you may require.
See the Installing-packages for details. The
list of available packages can be found at http://cran.r-project.org.
# Example `init.r` file install.packages("nlme", dependencies = TRUE)
R packages can also be included in your project source and installed when the
init.r file is executed.
install.packages("optional-path-to-packages/local-r-package-file.tar.gz", repos=NULL, type="source")
You can also run the R console application as follows:
$ heroku run R
q() to exit the console when you are finished.
Note that the Heroku slug is read-only, so any changes you make during the session will be discarded.
Scheduling a recurring job
You can use the Heroku scheduler to schedule a recurring R process.
The following command would run
R -f ./prog.r --gui-none --no-save
Using in your applications
This buildpack can be used in conjunction with other supported language stacks on Heroku by using the heroku-buildpack-multi buildpack.
See the example test applications which show how to use R from the console and various other examples.
The binaries used by the buildpack are hosted on AWS S3 at s3://heroku-buildpack-r.
See the building guide for building the R binaries yourself.
Optionally, the R version and buildpack version can be configured by providing a
.r-buildpack-version file in the root directory.
These files should contain 1 line of text containing the respective version. See alternate-versions for an example.
The following versions are available:
|R Version||Buildpack Version||Binary|
Due to the size of the R runtime, the slug size on Heroku, without any additional packages or program code, is approximately 90Mb.
If additional R packages are installed by the
init.r script then the slug size will increase.
Original inspiration from Noah Lorang's Rook on Heroku project.
MIT License. Copyright (c) 2013 Chris Stefano. See MIT_LICENSE for details.