I just put a fresh install of Ubuntu Server (10.04.4 LTS) on one of our machines. As I was doing some post-install config, I accidentally installed Rstudio Server. And subsequently fell down an exciting little rabbit-hole of server configuration and “ooooh-lala!” playtime.
A friend sung the wonders of Rstudio Server to me recently, and I filed it under “things to ignore for now”. Just another thing to learn, right? Turns out, the Rstudio folks do *great* work and write good docs, so I hardly had to learn anything. I just had to dust off my sysadmin skills and fire up some google.
I’m a little concerned about running web services on public-facing machines. Even more so, given that R provides fairly low-level access to operating system services. Still, I was impressed to see system user authentication.
I followed the docs for running apache2 as a proxy server, and learned a little about apache in the process. Since I made it this far, I figured I’d run it through https/ssl, add some memory limitations, etc. I’m still not entirely convinced this is secure — it seems that running it in a virtual machine or chroot jail would be ideal.
On the other hand, I ran across this post on running Rstudio Server inside Amazon EC2 instances. Nighttime EC2 spot prices on “Quadruple Extra Large” instances (68.4 GB of memory,
8 virtual cores with 3.25 EC2 Compute Units each) fell below $1 an hour tonight, which is cheap enough to play with for an hour or two — take it through some paces and see how well it does with a *very* *large* *job* or two. Instances can now be stopped and saved to EBS (elastic block storage), and so only need to be configured once, which really simplifies matters. In fact, I’m wondering if Rstudio (well, R, really) is my “killer app” for EC2.
Overall, I was really impressed at how fast and easy this was to get up and running. Fun times ahead!